I don't need to enumerate the pathname space, I need to read the documentation of spawn.

The new process is inheriting the root directory and curernt working directory of the parent.

So

If the parent's node is named 'parent' and the name of the node on which the new process is spawned is named 'child' 
then:

current working directory of parent is: /home/bob

root dir of the new child process is:  /net/parent/
current working directory of the child is: /net/parent/home/bob

So...when calling resmgr_attach(), and you specify /subdir/name, in reality it is doing the following:

/net/parent/subdir/name

But.../subdir/name doesn't show up if you do an 'ls' on parent.  But if you do an ls on the child as in: ls /net/parent/
 .... then you will see it.

I understand the logic, but I really really want my remote spawn'd process to be able to register at the root of the 
pathname space of the node on which it was spawned.

I see the 'on' utility (if using the -f argument) chroot's to the destination node's root directory before calling 
spawn(), which makes sense.  Unless there is a way to chroot back, this isn't terribly useful to us.


So the question is, how do I get resmgr_attach() to go to the root of the local node, so that if I do a 'ls' on a 
console running on the local node, I will see /subdir?

Me thinks that it would be a way around chroot() and probably won't be allowed?

Thanks
Kevin