[Vserver] update on gentoo guest shutdown
I don't comprehend the verver.stop script :( however I can tell you the fail/timeout is external to the gentoo guests by this test I enter the guest via vserver guest enter. i type halt 0 within seconds i am tossed back into the host and looking at processes the vserver lock process kills itself in about 5 seconds.. then if i run vserver guest stop it says the guest is not running. I am sure there are numerous reasons for not doing this, but why not just execute init 0 within the guest from the vserver script while it does the rest of its cleanup? -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] update on gentoo guest shutdown
On Tuesday 20 September 2005 10:05 am, Chuck wrote: correction. within the guest i typed init 0 anyway i tried from the host: vserver guestname exec init 0 and it shut down within seconds perfectly with no errors when i try vserver guestname stop it returns that the server is not running startup delivers no errors after stopping it in that fashion is this a clue or am i bypassing some important steps the 'stop' command does? I don't comprehend the verver.stop script :( however I can tell you the fail/timeout is external to the gentoo guests by this test I enter the guest via vserver guest enter. i type halt 0 within seconds i am tossed back into the host and looking at processes the vserver lock process kills itself in about 5 seconds.. then if i run vserver guest stop it says the guest is not running. I am sure there are numerous reasons for not doing this, but why not just execute init 0 within the guest from the vserver script while it does the rest of its cleanup? -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] update on gentoo guest shutdown
Chuck wrote: On Tuesday 20 September 2005 10:05 am, Chuck wrote: correction. within the guest i typed init 0 anyway i tried from the host: vserver guestname exec init 0 and it shut down within seconds perfectly with no errors when i try vserver guestname stop it returns that the server is not running startup delivers no errors after stopping it in that fashion is this a clue or am i bypassing some important steps the 'stop' command does? I don't comprehend the verver.stop script :( however I can tell you the fail/timeout is external to the gentoo guests by this test I enter the guest via vserver guest enter. i type halt 0 within seconds i am tossed back into the host and looking at processes the vserver lock process kills itself in about 5 seconds.. then if i run vserver guest stop it says the guest is not running. I am sure there are numerous reasons for not doing this, but why not just execute init 0 within the guest from the vserver script while it does the rest of its cleanup? Just an observation here Do you actually _know_ that the init-scripts are being run? Stopping the vserver should first run those to stop the services (apache, databases, etc) in a nice way, and thereafter stop the whole vserver. Is it possible for you to check? If it actually works, one could easily edit the vserver script to change the way 'stop' works, at least until a bugfix is available officially... :-) Best regards Tor Rune Skoglund ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver