Hi,

> > I tried to build a vserver using:
> > 
> > # ./vserver-build --force -m yum -n dns-int1 --hostname 
> > ns2-int.domain.dk --netdev=eth0:0 --interface=192.168.3.27 
> > --netmask=255.255.255.0 -- -d wbel4
> 
> you certainly do not want to specify eth0:0 which isn't an 
> interface but at best an alias ... if you want to get an 
> alias (why would you need it for? ... ah ifconfig, I see :) 
> then better use something like:
> 
>  --interface hansi=eth0:192.168.3.27/24

I found out - it creates its own virtual interface ;-)

Anyway - stopping the vserver still gives:

> > # vserver dns-int1 stop
> > Shutting down system logger:                               [  OK  ]
> > Starting killall:                                          [  OK  ]
> > A timeout occured while waiting for the vserver to finish 
> and it was 
> > killed by sending a SIGKILL signal. Please investigate the reasons 
> > and/or increase the timeout in apps/vshelper/sync-timeout.

Even though nothing particular has been started inside the vserver..

And one of the last things: If I need to run qmail inside one of the
vservers, I guess it should be created with "--initstyle fakeinit" ??

As far as I remember, there is an issue with bind - it should have
CAP_SYS_RESOURCE set (at least it was so in the old-style config). Where
should this parameter be added in the 2.0-style configuration ?

Regards,
/Brian
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to