update hogging CPU again in 2.0.2x

Jon Lewis (jlewis@inorganic5.fdt.net)
Thu, 31 Jul 1997 00:20:44 -0400 (EDT)


On an otherwise idle system...no users but me, just a very unbusy
ApacheSSL server running.

root 13 99.9 0.5 840 80 ? S 16:04 342:24 update (bdflush)
crash:~$ uptime ; uname -a
12:11am up 259 days, 9:35, 1 user, load average: 0.02, 0.17, 0.14
Linux crash 2.0.25 #6 Wed Nov 13 17:11:18 EST 1996 i486

This is the second time I've seen this happen after an exceptionally long
uptime. The last time was at 248 days with 2.0.23 on a different system.

Both are slackware 2.3 based, and have likely not had update upgraded.

Should I quit going for long uptimes and just reboot regularly?

I still have a 1.2.13-lmp system at 451 days and counting.

------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
________Finger jlewis@inorganic5.fdt.net for PGP public key_______