Nick Burrett wrote:
>
> Ben Kennish <[EMAIL PROTECTED]> writes:
>
> > 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.)
>
> Try building MySQL, or running `top' or `ps' without /proc mounted.
OK - point taken.
>
> > 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?
>
> Sounds like the VS is not shutting down properly. Does it happen
> with --restart ?
It doesn't happen at all now that Im using the latest CVS main source
build (and in fact, 'vsboot --*' is a lot more verbose and friendly.)
However, one thing that still puzzles me is that the length of time that
'rebootvs' on a VS takes. I know that this is due to bind problems but
surely a 'vsboot --restart' should take the same time as a 'rebootvs' if
you have only 1 VS?
Thanks
Ben
------------------------- 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
-----------------------------------------------------------------------------
