Björn Steinbrink wrote:
Did you build your kernel with CONFIG_SECURITY enabled? If so, make sure
that you also enabled CONFIG_SECURITY_CAPABILITIES and that the module
is loaded if it was built as a module. Otherwise the default capability
handling is disabled and your vserver is therefore allowed
On Wednesday 13 October 2004 06:35, David MacKinnon wrote:
Gregory (Grisha) Trubetskoy wrote:
I had something similar happen, but then it turned out the problem was
with my config. I figured it out by inserting an occasional echo
statement into
Herbert Poetzl wrote:
ip addr show
could you attach the output here please?
I'll post it tomorrow when I'm back at work. Hard to get the output
remotely when the machine drops off the network :)
As an aside, if I use the legacy vserver support (put in an apropriate
.conf file in
Hi,
here is the strace of the last action of a vserver stop
- reboot - :-)
...
...
Rebooting...
execve(/sbin/reboot, [reboot, -d, -f, -i], [/* 23 vars */]) = 0
uname({sys=Linux, node=distcc, ...}) = 0
brk(0) = 0x804b000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE,
On Wed, 13 Oct 2004 13:39:53 +1000
David MacKinnon [EMAIL PROTECTED] wrote:
Just ran into this today one some new servers I'm setting up.
util-vserver 0.30.195 (but it happened with 190 as well)
vserver 2.6 patch 1.9.2 on 2.6.8.1 (with dm/drbd and nfs patches)
When I stop _any_ vserver,
On Wednesday 13 October 2004 15:32, Björn Steinbrink wrote:
On Wed, 13 Oct 2004 13:39:53 +1000
David MacKinnon [EMAIL PROTECTED] wrote:
Just ran into this today one some new servers I'm setting up.
util-vserver 0.30.195 (but it happened with 190 as well)
vserver 2.6 patch 1.9.2 on
On Wed, Oct 13, 2004 at 12:16:16PM +0200, Christian Mayrhuber wrote:
On Wednesday 13 October 2004 06:35, David MacKinnon wrote:
Gregory (Grisha) Trubetskoy wrote:
I had something similar happen, but then it turned out the problem was
with my config. I figured it out by inserting an
On Wed, Oct 13, 2004 at 04:00:17PM +0200, Christian Mayrhuber wrote:
On Wednesday 13 October 2004 15:32, Björn Steinbrink wrote:
On Wed, 13 Oct 2004 13:39:53 +1000
David MacKinnon [EMAIL PROTECTED] wrote:
Just ran into this today one some new servers I'm setting up.
util-vserver
Just ran into this today one some new servers I'm setting up.
util-vserver 0.30.195 (but it happened with 190 as well)
vserver 2.6 patch 1.9.2 on 2.6.8.1 (with dm/drbd and nfs patches)
When I stop _any_ vserver, it brings down _both_ eth0 and eth1 (leaving
only lo up).
This happens with vservers
I had something similar happen, but then it turned out the problem was
with my config. I figured it out by inserting an occasional echo statement
into /usr/local/lib/util-vserver/vserver.functions (disableInterfaces() is
the func you'd probably be most interested in) to see what 'ip' commands
10 matches
Mail list logo
