Hello John,
On Wed, 21 Dec 2011 01:06:42 -0600 John Alberts wrote:
> I had the same problem a while ago upgrading to something above 2.6.32 I
> think. The solution was to put restart script in a vshelper directory.
>
Thanks for that input, alas it doesn't work. I tried it both with the
script in .defaults and the individual vserver config tree.
When the script is present (and executable) reboot -f will take a second
or so for the prompt to return.
No output and no action, the vserver stays up.
Any other ideas? Obviously this is doing something but not quite what's
desired. ^.^
> For each guest on the host, put the following:
>
> cat /etc/vservers/<guestname>/apps/vshelper/restart
> #!/bin/bash
>
> echo "vserver <guestname> restart" | at now
>
>
> Once you do that, 'reboot -f' should work again.
>
> John
>
>
> On Tue, Dec 20, 2011 at 11:43 PM, Christian Balzer <chibi@gol.com> wrote:
>
> >
> > Hello,
> >
> > Client OS is Debian Squeeze, identical install in both cases.
> > Host OS is also Debian Squeeze with custom kernel.
> > Older one runs:
> >
> > Kernel: 2.6.33.5-vs2.3.0.36.30.4
> > VS-API: 0x00020305
> > util-vserver: 0.30.215; Jun 18 2010, 13:35:17
> >
> > Newer one runs:
> > Kernel: 3.0.7-vs2.3.1
> > VS-API: 0x00020308
> > VCI: 0x0000000013001f11
> > util-vserver: 0.30.216-pre2986; Aug 29 2011, 07:49:51
> >
> > As the tin says, reboot -f inside a guest works on the old one, but
> > not on the new one.
> > That is, on the new one it will shut down, but not restart.
> >
> > Regards,
> >
> > Christian
> > --
> > Christian Balzer Network/Systems Engineer
> > chibi@gol.com Global OnLine Japan/Fusion Communications
> > http://www.gol.com/
> >
>
>
>
-- Christian Balzer Network/Systems Engineer chibi@gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/Received on Wed Dec 21 08:22:50 2011