Re: [Vserver] I'm in trouble now ....

2005-03-28 Thread Herbert Poetzl
On Mon, Mar 28, 2005 at 06:36:39PM +0200, Herbert Poetzl wrote: > On Mon, Mar 28, 2005 at 09:09:01AM -0500, Paul S. Gumerman wrote: [all the funny details zapped] > please give the testme.sh script (version 0.11) a try > (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh) Linux-VServer Test [V0

Re: [Vserver] util-vserver 1.9.5 configuration questions

2005-03-28 Thread Herbert Poetzl
On Mon, Mar 28, 2005 at 08:28:49PM +0400, Peter V. Saveliev wrote: > ... > > Now I plan to migrate to 1.9.5 & 2.6.11, 'cause of resource limits; and I > have > some questions: > > 1) is it right, that I've to create one directory > > /etc/vservers//interfaces/ > > per interface and there can

Re: [Vserver] I'm in trouble now ....

2005-03-28 Thread Herbert Poetzl
On Mon, Mar 28, 2005 at 09:09:01AM -0500, Paul S. Gumerman wrote: >Enrico --- thanks for the quick help. >The kernel is compiled with SELINUX, but also compiled with SELINUX >disabled. >The thing is, this was all working fine a short time ago; I'm >completely boggle

[Vserver] util-vserver 1.9.5 configuration questions

2005-03-28 Thread Peter V. Saveliev
... Now I plan to migrate to 1.9.5 & 2.6.11, 'cause of resource limits; and I have some questions: 1) is it right, that I've to create one directory /etc/vservers//interfaces/ per interface and there can be only one address on such interface? I didn't read the code, I'll do it while going to

Re: [Vserver] I'm in trouble now ....

2005-03-28 Thread Paul S. Gumerman
Enrico --- thanks for the quick help. The kernel is compiled with SELINUX, but also compiled with SELINUX disabled. The thing is, this was all working fine a short time ago; I'm completely boggled!  Should I recompile with those CFLAGS next, or what? Enrico Scholz wrote: [EMAIL PROTECTED]

Re: [Vserver] I'm in trouble now ....

2005-03-28 Thread Enrico Scholz
[EMAIL PROTECTED] ("Paul S. Gumerman") writes: > Ran "vserver fc3-reference hashify", which ran ok with one message > (sorry, can't recall it now). The exact message would be helpful perhaps. > Then tried "vserver loco-reference hashify" which failed with a > message saying "vserver ... suexec