Subject: Re: [vserver] veserver context stop problemematic ?
From: "Daniel Hokka Zakrisson" <daniel@hozac.com>
Date: Thu, 10 Jan 2008 17:12:51 +0100 (CET)

Xavier de Poorter wrote:
> Hi everyone,
>
> vserver vsbase2 stop
>   * Stopping system log daemon...
>                                                   [ OK ]
>   * Terminating all remaining processes...
>                                                          killall5: can't
> read sid for pid 1
>
>
>                                                   [ OK ]
>   * Sending all processes the KILL signal...
>                                                          killall5: can't
> read sid for pid 1

Definitely ignorable, though we might want to hide that in the future...

>
>                                                   [ OK ]
>   * Will now restart
> /usr/lib/util-vserver/vserver.stop: line 85: 14496 Killed
>     "${NICE_CMD[@]}" "${CHBIND_CMD[@]}" "$_VTAG" --migrate
> "${OPTS_VTAG_ENTER[@]}" --silent -- $_VCONTEXT $SILENT_OPT --migrate
> --chroot --xid "$S_CONTEXT" -- "${INITCMD_STOP[@]}"

This means the rc-script committed suicide. You can probably work around
that, but in general, it's ignorable too.

> Is it problematic ?
>
> util-vserver 0.30.214-1
> vserver-debiantools 0.5.0
>
> testme.sh
> Linux-VServer Test [V0.17] Copyright (C) 2003-2006 H.Poetzl
> chcontext is working.
> chbind is working.
> Linux 2.6.22.15-vs2.2.0.5-xxxx-std-ipv4-32 #2 SMP Wed Jan 9 14:43:54 CET
> 2008 i686
> Ea 0.30.214 273/glibc (Sa) <v13,net,v21,v22,v23,netv2>
> VCI: 0002:0200 273 030007b1 (TbsPHIW)
> ---
> [000]# succeeded.
> [001]# succeeded.
> [011]# succeeded.
> [031]# succeeded.
> [101]# succeeded.
> [102]# succeeded.
> [201]# succeeded.
> [202]# succeeded.
>
>
>


-- 
Daniel Hokka Zakrisson