thanks to Shawn and Jose, the risc-v port is moving along well. we have
network, ratrace works, which is proving handy, it boots as a cpu server,
shawn brought an fdt parser in, and so on.

I am having a problem I don't understand when I try to cpu into the bpif3.
Shawn reports this works for him.

I have a thinkpad serving as as fs/auth server. I can cpu into it no
problem.

The riscv board is coming up, and starting many services, using my thinkpad
as its auth and fs.

But when riscv board tries to start services I get this:
bpi Jul  2 08:51:49 started on tcp
bpi Jul  2 08:51:49 couldn't fork for tcp!*!17019
bpi Jul  2 08:51:49 couldn't fork for tcp!*!17020
bpi Jul  2 08:51:49 couldn't fork for tcp!*!17020

It's been a long time since I debugged this sort of thing ...
I try listen1:
aux/listen1 -1tv tcp!*!17019 tcp17019
listen started
incoming call for tcp!*!17019 from 192.168.0.20 in /net/tcp/2
tlssrv: auth_proxy: auth_proxy short read

This is some simple thing I know I'm missing, I'm wondering what.

thanks

------------------------------------------
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/Te234c982c7b38907-M73c71063ccda8215e9596ab4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Reply via email to