Boris Kolar wrote:
> Daniel Hokka Zakrisson wrote:
>
>>Oliver Welter wrote:
>>
>>>this is more or less expected behaviour...
>>
>>With recent patches, i.e. 2.0.2-rc11+ or 2.1.0+, you can also set the
>>persistent flag to keep the context around even after all processes die.
>>For util-vserver, this means adding ^38 to the flags file.
>
>
> Is this the default? I now realize it's not a bug, it's a feature ;) But
> it should be fixed anyway, because if you don't know how vserver works,
> it can be very puzzling. I disabled all services before my first attempt
> to start vserver, so I spent quite a few hours to figure out what's
> going on.
No, and it shouldn't be. This is not the behaviour most people expect,
and to shutdown such a guest you have to run vattribute --set --xid
<name/xid> --flag ~^38, so vserver ... stop is not sufficient.
-- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Thu Mar 30 13:38:11 2006