Re: [Cooker] Xscreensaver keeps multible processes alive (atleast with solarwinds-module)
Am Dienstag, 14. Januar 2003, 10:32:29 Uhr MET, schrieb Frederic Crozat: > I think the problem is in rss_glx, since default GNOME Mdk screensaver use > chbg with xscreensaver without any problem.. Yes, this could be the problem. Please file a bug report to the author: Tugrul Galatali CU -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
Re: [Cooker] Xscreensaver keeps multible processes alive (atleast with solarwinds-module)
On Tue, 14 Jan 2003 11:21:05 +0200, mika.laiti wrote: > This is a multipart message in MIME format. > --=_alternative 00336496C2256CAE_= > Content-Type: text/plain; charset="us-ascii" > > I noticed that my system used to be very slow. I used top-command and > noticed that I had multible solarwinds processes running and they were > eating all of my resouces. > I am using newest uptodate cooker with gnone with XScreensaver enabled and > I have selected solarwinds gl-module. > Because I was using my system, the xscreensaver were stopped and therefore > I think that all solarwind processes should also have been killed, which > was however not the case. > Here is my top-output > > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ Command > 3535 lamikr19 10 2016 2016 1468 R 7.1 0.4 9:01.54 solarwinds > 3515 lamikr20 10 2308 2308 1452 R 6.7 0.4 18:59.68 solarwinds > 3517 lamikr20 10 2072 2072 1468 R 6.7 0.4 18:22.76 solarwinds > 3597 lamikr17 10 2308 2308 1452 R 6.7 0.4 1:29.33 solarwinds > 3600 lamikr17 10 1996 1996 1452 R 6.7 0.4 1:08.49 solarwinds > 3603 lamikr17 10 1996 1996 1452 R 6.7 0.4 0:49.14 solarwinds > 3606 lamikr17 10 1996 1996 1452 R 6.7 0.4 0:30.79 solarwinds > 3512 lamikr19 10 2340 2340 1452 R 6.4 0.5 20:24.38 solarwinds > 3580 lamikr17 10 2340 2340 1452 R 6.4 0.5 1:52.43 solarwinds > 3538 lamikr17 10 2340 2340 1452 R 6.1 0.5 8:26.57 solarwinds > 3575 lamikr17 10 2308 2308 1452 R 6.1 0.4 2:16.31 solarwinds > 3529 lamikr17 10 2072 2072 1468 R 5.8 0.4 10:27.01 solarwinds > 3532 lamikr17 10 2300 2300 1452 R 5.8 0.4 9:41.69 solarwinds > 3540 lamikr17 10 2016 2016 1468 R 5.8 0.4 7:51.69 solarwinds > 3558 lamikr17 10 1996 1996 1452 R 5.8 0.4 7:46.54 solarwinds > 3672 lamikr15 0 968 968 752 R 1.9 0.2 0:00.22 top > 3612 lamikr 9 0 12972 12m 7024 S 1.3 2.5 0:05.57 > gnome-terminal > > I rebooted the my computer just for safe and was able to reproduce the > problem very easily. > > 1) Boot to gnome > 2) Enable XScreensaver and select solarwinds > 3) Let the screensaver start and run for a while > 4) Activate computer so that xsreensaver deactivates > 5) Use top and notice solarwinds processes > > My system is following: > Mandrake cooker, > kernel-2.4.21.pre2.1mdk-1-1mdk (acpi off) > xscreensaver-4.06-3mdk > rss_glx-0.7.0-1mdk (from contribs, I think that that includes > solarwinds module) > > AMD K6-3 400 mhz > Nvidia TNT2 > > I am not sure whether I should create a bug from this because the problem > may as well be in the contrib-package than in the xcreensaver itself... I think the problem is in rss_glx, since default GNOME Mdk screensaver use chbg with xscreensaver without any problem.. And btw, could you refrain from posting in HTML ? Thanks :) -- Frederic Crozat MandrakeSoft
[Cooker] Xscreensaver keeps multible processes alive (atleast with solarwinds-module)
I noticed that my system used to be very slow. I used top-command and noticed that I had multible solarwinds processes running and they were eating all of my resouces. I am using newest uptodate cooker with gnone with XScreensaver enabled and I have selected solarwinds gl-module. Because I was using my system, the xscreensaver were stopped and therefore I think that all solarwind processes should also have been killed, which was however not the case. Here is my top-output PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ Command 3535 lamikr 19 10 2016 2016 1468 R 7.1 0.4 9:01.54 solarwinds 3515 lamikr 20 10 2308 2308 1452 R 6.7 0.4 18:59.68 solarwinds 3517 lamikr 20 10 2072 2072 1468 R 6.7 0.4 18:22.76 solarwinds 3597 lamikr 17 10 2308 2308 1452 R 6.7 0.4 1:29.33 solarwinds 3600 lamikr 17 10 1996 1996 1452 R 6.7 0.4 1:08.49 solarwinds 3603 lamikr 17 10 1996 1996 1452 R 6.7 0.4 0:49.14 solarwinds 3606 lamikr 17 10 1996 1996 1452 R 6.7 0.4 0:30.79 solarwinds 3512 lamikr 19 10 2340 2340 1452 R 6.4 0.5 20:24.38 solarwinds 3580 lamikr 17 10 2340 2340 1452 R 6.4 0.5 1:52.43 solarwinds 3538 lamikr 17 10 2340 2340 1452 R 6.1 0.5 8:26.57 solarwinds 3575 lamikr 17 10 2308 2308 1452 R 6.1 0.4 2:16.31 solarwinds 3529 lamikr 17 10 2072 2072 1468 R 5.8 0.4 10:27.01 solarwinds 3532 lamikr 17 10 2300 2300 1452 R 5.8 0.4 9:41.69 solarwinds 3540 lamikr 17 10 2016 2016 1468 R 5.8 0.4 7:51.69 solarwinds 3558 lamikr 17 10 1996 1996 1452 R 5.8 0.4 7:46.54 solarwinds 3672 lamikr 15 0 968 968 752 R 1.9 0.2 0:00.22 top 3612 lamikr 9 0 12972 12m 7024 S 1.3 2.5 0:05.57 gnome-terminal I rebooted the my computer just for safe and was able to reproduce the problem very easily. 1) Boot to gnome 2) Enable XScreensaver and select solarwinds 3) Let the screensaver start and run for a while 4) Activate computer so that xsreensaver deactivates 5) Use top and notice solarwinds processes My system is following: Mandrake cooker, kernel-2.4.21.pre2.1mdk-1-1mdk (acpi off) xscreensaver-4.06-3mdk rss_glx-0.7.0-1mdk (from contribs, I think that that includes solarwinds module) AMD K6-3 400 mhz Nvidia TNT2 I am not sure whether I should create a bug from this because the problem may as well be in the contrib-package than in the xcreensaver itself... Mika
