From: Herbert P÷tzl (herbert_at_13thfloor.at)
Date: Wed 27 Aug 2003 - 12:54:39 BST
On Wed, Aug 27, 2003 at 12:09:37PM +0200, desman_at_gmx.de wrote:
> in /usr/sbin/vserver
> nothing of the followed words can be found:
> Host name
> security context
> Kernel do not support chrootsafe(), using chroot()
> Usage: init 0123456SsQqAaBbCcUu
> I ran out of ideas, as it seems to me i have to read and understand the
> whole vserver script to
> get an idea why he tells me "Usage: init 0123456SsQqAaBbCcUu"
this is probably because your init gets a wrong argument
(one that is not in [0123456SsQqAaBbCcUu])
the next question should be, why does init require an
argument? and I guess this can be answered with: because
in this case init is a multicall binary, which, depending
on the situation, acts as init process or as command line
utility to message such an init process ...
I would suggest you simply try for example the minit
or any other lightweight init instead ...
> In the vserver script by default init3 is started, normaly the right one.
> I can`t try vserver 0.22 because it doensn`t work with ctx17a
yes but you could patch ctx17 and try 0.22 then, but I guess
it will fail too ... nevertheless it would be interesting
to know ...
> -----Original Message-----
> From: Mike Fischer [mailto:mike.fischer_at_ipsi.fraunhofer.de]
> Sent: Mittwoch, 27. August 2003 11:44
> To: vserver_at_solucorp.qc.ca
> Subject: Re: [vserver] How to get suse 8.2 to work ?
> desman_at_gmx.de wrote:
> > hi,
> > i already took S_FLAGS="lock nproc sched fakeinit" into my config
> > vserver1:/etc/vservers# vserver suse82 start
> > Starting the virtual server suse82
> > Server suse82 is not running
> > ipv4root is now 22.214.171.124
> > Host name is now twice
> > New security context is 30
> > Kernel do not support chrootsafe(), using chroot()
> > Usage: init 0123456SsQqAaBbCcUu
> This last line is most probably what's going wrong.
> Look thorugh your vserver script to see what is being called at that point.
> I have the stuff running under SuSE 8.2 with the 2.4.20 Kernel but with
> the 22 tools, so I can only tell you that it works but not which line
> your problem is :(