Figured it out... /var was full! apt-get clean to the rescue. :)
> On 20030305.1143, Rob Hudson said ... > > Looking at the man-db file in /etc/cron.daily, if I run this command: > > start-stop-daemon --start --pidfile /dev/null --startas /usr/bin/mandb \ > --oknodo --chuid man -- --no-purge > > The thing runs and runs and doesn't stop. > > The thing is that this thing used to run, along with all the other stuff > in cron.daily and didn't have this problem. So something's wrong. > Don't know what it is. > > -Rob > > > On 20030305.1110, Beaker (aka Jeff W) said ... > > > > Rob Hudson wrote: > > > Every morning when I come to my workstation at work (Debian testing), my > > > CPU is maxed out at 100%. If I look at top, I see mandb is taking up > > > 100% CPU. Looking at my process tree shows this: > > > <snip> > > > Anyone have an idea of what's going on and how I can fix it? > > > > from http://www.fifi.org/cgi-bin/man2html/usr/share/man/man8/mandb.8.gz > > > > mandb(8) > > NAME > > mandb - create or update the manual page index caches > > > > --- > > > > I'd guess that this is getting called from your daily cron file and > > isn't niced down => it hogs your cpu. Chances are you don't need to > > update your manpage DB every night... :) > > > > -beaker > _______________________________________________ > Eug-LUG mailing list > [EMAIL PROTECTED] > http://mailman.efn.org/cgi-bin/listinfo/eug-lug _______________________________________________ Eug-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
