>> no, it doesn't. on plan 9, when the shell script exits, >> nothing will have vacfs mounted anymore, so vacfs >> will get an eof on the 9p connection and exit. >> that's why i put an rfork n in the script. > > aha, that's probably what the rfork call does ?
rfork n forks the name space, so that any changes made by the script don't propagate out to the parent process. This means that (1) vacfs can mount on /n/vac without any fear of bothering some other instance of the script, and (2) when the script exits, there will be no more references to the mounted /n/vac and the kernel will unmount it. If you want simple, you should run Plan 9. > Meanwhile I've hacked up vacfs to give it an "autodie" mode. > It means: automatically terminate if the last file has been > closed. Seems to work, but now idea how stable it would be > in production ;-o In the time it took you to do that you could probably have written unvac instead. Russ
