On Thu, Jan 10, 2008 at 05:18:52PM +0100, Xavier de Poorter wrote:
> Raoul Bhatia [IPAX] a écrit :
> >On Thu, 2008-01-10 at 15:57 +0100, Xavier de Poorter wrote:
> >>thanks raoul
> >>if the vserver mechanism kill himself the unshutdowned processes then i
> >>choose the 1)
> >
> >i do not know for sure but i think it does.
> >
> >>and what about this ? :
> >>/usr/lib/util-vserver/vserver.stop: line 85: 9101 Killed
> >> "${NICE_CMD[@]}" "${CHBIND_CMD[@]}" "$_VTAG" --migrate
> >>"${OPTS_VTAG_ENTER[@]}" --silent -- $_VCONTEXT $SILENT_OPT --migrate
> >>--chroot --xid "$S_CONTEXT" -- "${INITCMD_STOP[@]}"
> >
> >i think this is related to the init scripts too. it should either come
> >from S30urandom or S90reboot. i think the vserver is not allowed to do
> >something it wants to do - e.g. set/get/save the system time and/or
> >urandom state.
> >
> >try to put some output into those files and you will see where it
> >happens.
> >
> >cheers,
> >raoul
>
> update-rc.d -f reboot remove
> and the vserver stop cleanly ! thanks again :-)
>
> i removed almost all startup scripts : what are the mandatories ones ?
> i guess they are rc rc.local rcS and sysklogd
well, you need at least one service to be running, unless
you enable persistant context support for the guest.
besides that, it's 100% your choice ...
> cordialement,
> xavier
>
Received on Thu Jan 10 17:05:19 2008