-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not able to reproduce this problem, but perhaps xsysinfo is causing your system to use a lot of memory. (On my system, it doesn't appear to have any sort of memory leak.) On a comannd-line, could you find out the PID of xsysinfo and then submit the contents of /proc/<pid>/status?
BTW, regarding it taking a lot of CPU even at the xdm login screen, I'm not sure how xsysinfo is running if there isn't an active X session on the machine. Could you elaborate? Thank you, tony Pierre Bauduin wrote: > Package: xsysinfo > Version: 1.7-5 > > The version of xsysinfo that comes with Debian 4.0 "etch" has some major > issues. > It uses a lot of CPU and memory all the time. > > Even when you're at the xdm login screen (nobody is logged), > If xsysinfo isn't running, the load average is around 0.9 > If xsysinfo is running, the load average is around 5.0 > > Take a look at the following screenshot: > http://pierre.baudu.in/files/2007-03-07-095221_1024x768_scrot.png > > You can very well see that: > - load average is 5.0 when xsysinfo is running and 1.0 when it is not > running > - at the time of the screenshot the load average is 4.50 > - at the time of the screenshot 560 MB out of 640 MB of swap are being used > > Debian release: 4.0 "etch" > Architecture: i386 > CPU: Pentium III (Katmai) at 450 MHz > Memory: 256 MB > Kernel: Linux cobra 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 > GNU/Linux > Version of packages xsysinfo depends on: libc6 (>= 2.3.6-6), libice6, > libsm6, libx11-6, libxaw7, libxext6, libxmu6, libxpm4, libxt6 > > It would be nice if someone could look into this :) > > Thank you, > -- > Pierre Bauduin > Linux enthusiast since 1996 > Debian GNU/Linux user > website: http://pierre.baudu.in/ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF7vOapdwBkPlyvgMRAshXAJ9vKnrsrMM5PoW1onQVGeim+XG+jgCeIPvk 7F4GNqUDz2XAlsM9F8uv2QE= =8MDV -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
