Re: [9fans] xcpu fix for Plan9.c

[kokamoto@hera.eonet.ne.jp]

I'm now at home, and playing with xcpu on two machine Plan 9
system, one for CPU/AUTH/Fossil file server and the other is a
terminal.

On the CPU server, I dispatched the command like:
venus# xcpusrv -s xcpu
then got the answer:
fsnetproc pid is 421
threadpostmountsrv RETURNS!~!!!!!!

Next, I did the command
venus# aux/listen1 -tv tcp!*!20001 /bin/exportfs -S /srv/xcpu
listen started

After this I moved to the terminal, and dispatched the command:
term# 9fs tcp!venus!20001 /mnt/xcpu
post...
Then, I listed the terminal's /mnt/xcpu directory, so

term# ls -l /mnt/xcpu
and got the answer:
--rw--rw--rw M 47 ssh ssh 0 Jan 1 1970 clone

Ok, Next I read the clone file, and got
65536term#   
Oops! I forgot open the clone file, then,

term# openclone /mnt/xcpu/clone&
and got,
term# 131072openclone: child exits, we exit too  <==== not 0/1

then,
term# ls -l /mnt/xcpu
and got
d-r-x-r-x-r-x M 47 ssh ssh 0 Jan 1 1970 131072
--rw-rw-rw- M 47 ssh ssh 0 Jan 1 1970 clone

Ok, then I dispatched the series of command in Ron's xcpu.pdf:

term# cp /bin/date /mnt/xcpu/131072/exec
term# echo date >/mnt/xcpu/131072/argv
term# echo exec >/mnt/xcpu/131072/ctl
term# cat /mnt/xcpu/131072/stdout   <=======

Then, I got the right answer as
Sat Oct 22 11:38:02 JST 2005

Ok, everything worked fine.

Then, I tried to do the above sequence of commands, and
got error such as
  error writing /mnt/xcpu/131072/exec: not connected.

So, my questions are:

1) why I got 131072 instead of 0 or 1?
    Am I on the right way?
2) why the /mnt/cpu/131072/exec file accepts cp command
    only once?

I know Ron has been very busy, and may be still...
I can wait Ron, don't work too hard!

Kenji