I wrote:
> Philippe Teuwen wrote:
>> Hello,
>>
>> Here are some problems I have with vserver.
>>
>> My environment:
>> Kernel: Debian vserver_pre-patched kernel for AMD64:
>> Linux version 2.6.17-2-vserver-amd64 (Debian 2.6.17-9)
>> (waldi@debian.org)
>> (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Wed
>> Sep
>> 13 18:02:36 CEST 2006
>> According to changelog.Debian, this version is using vserver patch
>> v2.0.2
>> util-vserver: 0.30.211-6
>>
>> First problem:
>> In some situations my CPU was burning like hell for days before I
>> noticed
>> it.
>> This was the vcontext/login process, the one running when using the
>> command "vserver XX enter".
>> If it happens that the process is disconnected from its terminal it eats
>> all the CPU :-(
>>
>> Apparently it happens when the session is not ended properly
>> (disconnections, etc)
>> I could reproduce the problem as follow:
>> * ssh to the server as normal user
>> * sudo su -
>> * vserver XX enter
>> * now from another term, kill -9 on either of the two su processes ("su
>> -"
>> or "-su")
>> At that point the session in the vserver ends but vcontext is still
>> hooked
>> to the
>> current terminal so cpu is fine.
>> * now quit the current terminal
>> At that point vcontext is not hooked to any terminal (vps ax => "?" on
>> the
>> tty column)
>> and using top you see it's running 100% cpu, ~ 80% system and 20% user.
>
> I'll look in to it.
I am unable to reproduce that here. The vlogin process does stick around,
which it probably shouldn't, but its resource usage is the same as it's
always been.
-- Daniel Hokka Zakrisson _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Thu Jan 18 05:09:20 2007