Hm. that's interesting, i thought it was only me! =) I've been running a updated potato for a good while now, but last night when the update and then upgrade (apt-get upgrade) i did was done, it would start running some of the same programs you have. It would fun up afterstep and thrash and eat resources. then gnome-panel would eat for a while and then it stopped doing it.
i thought it might have to do with the update in man-db, but i guess it isn't a very recent thing. sorry i can't be anymore helpful, i'm a victim too! =) Herbert Ho On Mon, 4 Oct 1999, Todd Suess wrote: > Ok, this is a good one. > > I ran a recent apt-get dist-upgrade to complete the upgrade needed > to fully bring my slink system up to potato. Since then, I have noticed > some very strange activity on my system. Every time I run an apt-get > anything (update, upgrade, etc), the following happens: > > 1. Apt-get action completes. > > 2. pdmenu fires up and proceeds to thrash the hard drive for about > 30 minutes, slowly chewing up all available system resources > (RAM and SWAP), until SWAP is down to 0k available. > > 3. pdmenu then stops, and all memory returns to normal. > > 4. afterstep fires up and proceeds to thrash the hard drive for about > 30 minutes, slowly chewing up all available system resources > (RAM and SWAP), until SWAP is down to 0k available. > > 5. afterstep then stops, and all memory returns to normal. > > **NOTE I am NOT running xwindows at this point, all I have open > is 2 VC's, one which I was running the apt-get on, and another > running top to monitor what is going on. > > This sequence continues with the running (at least in top) of all > my installed xwindows managers (fvm, olvm, etc), and when the > last one is done thrashing the hard drive (this has now taken about > 4 hours of time) , memory returns to normal, and the system > seems to be completely normal until I run another update, etc. > > This is very perplexing, I cannot imagine a reason why any of > my xwindow managers would load without xwindows even being > open (or even configured at this point). If anyone can suggest > ANY reason why this might be happening, I am very open to > suggestions. > > Regards, > > Todd > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
