Yes, you got two status reports today.  

Last night I noticed that the system clock was off by an hour because it
had been inadvertantly rebooted and the BIOS doesn't know Daylight Savings
Time from a hole in a bit mask.  So I reset the time.  And forgot where
the "seconds" went.  (mmddhhmmccyy.ss, go figure) And set the year to
2020.  This was no problem.  When I set the year back to 1999, it
triggered *every* timed job on the system... backups, security sweep, log
rotations, manual database rebuild, locate datebase rebuild, and, of
course, every nightly job for every mailing list.  At least *four* of
these processes touch every file on the system.  Needless to say, it
thrashed the disk a lot, system load shot through the roof, and it ran out
of physical memory and went to disk swap in a heartbeat... (do you hear a
recurring theme here?  When the system starts thrashing the disk,
performance goes out the window.) 

I killed off the jobs that were safe to kill (backups, disk sweeps, etc)
but decided that killing the nightly list maintenance jobs was probably a
bad idea.  So you got the results of two nightly jobs.  Sorry.

After things calmed down, I wanted to reboot the system and decided to
upgrade the memory while I had it down.  The SIMM swap went quickly and
the hardware recognized it just fine, but it caused funny errors during
Linux bootup (it thought a library was corrupt).  I swapped the memory
back out and things booted up just fine... so we're still running on just
20M of memory until I have time to sort out the problem.  (Which will be
soon... we're really needing that extra memory at this point.) 

--
Carl D Cravens (raven@phoenyx.net)
My reality check just bounced.

-- --------------------------------------------------------------
Listowner tools are found at http://www.phoenyx.net/listowners