From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sat 15 Nov 2003 - 12:07:25 GMT
On Sat, Nov 15, 2003 at 03:35:23AM -0500, Allen Parker wrote:
> init: timeout opening/writing control channel /dev/initctl
on a 'normal' server, init and telinit are often the
same binary, and the 'init' process knows that it is
init by verifying that it's pid equals 1 ...
when init is started, it opens a pipe, which reads
the commands given by telinit and halt, poweroff, etc.
possible causes for this message therefor are:
- init/telinit is called but not as pid == 1
- reboot, halt, poweroff are called without -f
- init is started as 'faked' pid 1 but this
doesn't work as expected yet ...
possible solutions:
- add some userspace tool outside the vserver
which opens/reads the pipe and acts accordingly
- find the 'bad' invocation and 'improve' it
or remove it, if not required
- demonstrate that it is a vserver misbehaviour
which requires some code change ;)
HTH,
Herbert
> util-vserver-0.24 kernel-2.4.22-vs1.00
>
> Allen Dale Parker
> allenp_at_efn.org
>
> "ego sum ens ompnipotens"
>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver