On Thu, 2011-09-22 at 04:45 +0200, olafbuddenha...@gmx.net wrote: > Hi, > > On Mon, Sep 05, 2011 at 06:42:22AM +0200, olafbuddenha...@gmx.net wrote: > > > As recently I aquired the (bad) habit of running my system 24/7, > > almost never voluntarily rebooting, I was able to make further > > observations. > > I totally forgot to mention another important bit: the growing swap > consumption can be triggered "reliably" simply by installing a lot of > Debian packages -- doing an "apt-get upgrade" for example. (I > occasionally observed growing memory usage with other commands doing I/O > on large amounts of data as well; but couldn't pinpoint any specific > situations so far... Perhaps it's just some randomly triggered bug > accumulating dead objects in memory or something like that?)
Regarding memory usage, when building packages that hangs/are interrupted many processes are not terminated and I see /usr/bin/faked-tcp and hurd/fifo instances still in the process list. Are there timeouts for dead processes? What does the STAT letters f,m, o, p, w stand for, they are not explained by the ps(1) man page, only uppercase ones (except s and l). Examples are: several /bin/bash -c fail=... in state Sw several /usr/bin/make in state Sw several /hurd/fifo in state So several /usr/bin/faked-tcp in state Ssfo several /bin/bash -noprofile /dev/fd/3 in state Sslo
