> 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.
I should have spent another minute looking at this before sending, but
FDT's being ping flooded and mail bombed simultaneously, so I'm kind of
rushed.
I straced update, and it looked perfectly normal. I tried killing it (had
to use -9), and just started a new one, and now it looks fine again...
root 24360 0.0 1.1 848 172 ? S Jul 20 0:00 update (bdflush)
hmm....
------------------------------------------------------------------
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_______