From: Christian Mayrhuber (christian.mayrhuber_at_gmx.net)
Date: Wed 13 Oct 2004 - 15:00:17 BST
On Wednesday 13 October 2004 15:32, Björn Steinbrink wrote:
> On Wed, 13 Oct 2004 13:39:53 +1000
> David MacKinnon <davidm_at_obsidian.com.au> 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 126.96.36.199 (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 on the same subnet as the host, or on
> > completely different networks.
> > I haven't come across this before, I have another box with 2.6.8 +
> > vs1.9.2 (no other patches) with util-vserver 0.30.190 that doesn't
> > exhibit this behaviour. Copying the config from this working machine
> > doesn't help at all.
> > Anyone come across this before? I suppose I'll try stripping out other
> > kernel patches, but I'm not wonderfully hopeful.
> 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 to
> remove the interfaces.
> Vserver mailing list
Thats it. At least for me...
modprobe capability does the trick.
Debian default kernel config setting is to compile it
as a module, but to not load it per default.
Very strange default setting.
-- lg, Chris
_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver