On Sun, Jan 14, 2007 at 12:09:36PM +0100, Philippe Teuwen wrote:
>
> >I'll look in to it.
> >
> Thanks,
> I just tried on the vanilla setup 2.6.17.14 + vs2.0.2.1-grsec2.1.9
> and I have the same cpu burning issue.
> So it has nothing to do with Debian kernels.
> Did someone else experienced the same problem when following
> the steps I presented in my first email?
haven't checked your steps yet, but it is very likely
that a vanilla (completely unpatched) kernel from
kernel.org will expose similar effects ...
> <http://people.linux-vserver.org/%7Eharry/patch-2.6.17.14-vs2.0.2.1-grsec2.1.9.diff>
>
> >Lots of programs overwrite the process name to get nicer ps/top/etc.
> >output.
> Ok
> >vkill needs the context too, i.e. vkill --xid devel 17111.
> >
> Ok but why killing from context 1 does not work?
because context 1 is the so called 'spectator context'
and not the admin context (which is xid=0 for now)
> chcontext --ctx 1 kill XXXX => silently fails
> chcontext --ctx ZZZZ kill XXXX => ok
yep, intentional
HTH,
Herbert
> Phil
>
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Mon Jan 15 21:59:45 2007