Why is it that FreeVSD has such a problem with the /proc 'directory' on
the VSs?...
1. Why does a VS need a proc directory anyway? 'Files' like 'meminfo'
and 'interrupts' dont really apply to one VS and might not be desirable
to let your users see (btw, I have just deleted all my test VSs so dont
quote me on those files being there.)
2. Whenever I do a vsboot --stop, pause, and do a vsboot --start now, I
get firstly a "umount: /proc device busy" followed, of course, by a
"mount: /proc device already mounted" message. Why is /proc busy upon
shutting down a VS?
3. This means that I can never fully delete a VS - I always get a /proc
directory remaining with the only solution (that I could find) being to
reboot the server and then "rm -rf /home/vsd/vs/vsone/proc"
OK so I know that this isnt a major thing but maybe something for the
next release ey Damion? ;-) (that was a joke btw)
See ya,
Ben K
[EMAIL PROTECTED]
www.fubra.com
(yes I've decided to use my .com email address now!)
------------------------- The freeVSD Support List --------------------------
Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives: http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------
