So far the wind hasn’t happened in a big way, maybe 15 MPH gusts or so and 3-4 constant.  There is eight hours left on the high wind warning though so might happen yet.  The barometer is taking another big dive here, down to 28.18 so far.  My sinuses are beginning to complain.  But the telephones are still working.

     There is a high wind warning for tomorrow predicting sustained winds of 40 MPH and gusts up to 60 MPH.  Almost invariably when we have winds of that magnitude I lose power, Internet, and phones here (Internet and phones being provided by Comcast, and Comcast distribution amplifiers require power to run).

     So if you call and the phone isn’t answered, please leave a message with your name, telephone number, user ID, and the nature of your call and I will return your call as soon as possible.

     The equipment is in a co-location facility with a big UPS and diesel backup generators so service should not be impacted.

     I applied some updates to one of the host machines and it caused a number of guest machines to reboot.  There was no advanced warning to me else I would have done this at a low traffic time.  I apologize for the interruption.

     I stumbled across this article in the Seattle Times regarding the hacker attack in 1995:

     http://community.seattletimes.nwsource.com/archive/?date=19950706&slug=2129929

     I thought I’d comment on a couple of factual issues twenty years after the fact.  First, the attack wasn’t particularly sophisticated, it took advantage of a race condition that existed in BSD mail and the fact that the old program was setuid root made it possible to abuse the condition to replace the password file.   It was a scripted attack.

    The FBI’s statement that the fact that it came across state lines made it within their jurisdiction is somewhat humorous.  I attempted to get the FBI’s involvement and their response to me was that if it didn’t involve at least half a million in losses, go away because they had bigger fish to catch.

     The client mail server has been imaged and returned to service.  This just provides a snapshot so it can be rapidly returned to service if it is damaged in some way.

     Mail server maintenance is rescheduled again.  Tonight (Sunday) 10ish.  I’m leaving some wiggle room on the time, sometime between 10pm-midnight, so I don’ t have to skip it if I’m in the middle of something at 10pm. Sorry, computers were not being nice to me last night.

     The planned mail server maintenance has been delayed.  Still working on borked server and seriously sleep deprived.  The server that I took out of service because it became unstable is a problem with an upgrade that didn’t go well.  The hardware itself survived stress testing and memory testing with no errors.

     The client mail server, mail.eskimo.com, which provides pop3, imap, and smtp for mail clients will be down from 10pm-10:20pm approximately to make a backup image this evening.

     During this time webmail and imap/pop/smtp from mail clients will be unavailable.  Mail can still be read via shell mailers like pine, elm, mush, heirloom BSD mail, etc, but outgoing will be down for that duration.

     The web server suffered a strange load spike this morning.  At 10AM I rebooted it because it was so loaded I couldn’t even determine the cause.

     I am concerned that 2.4.17, to which I recently upgraded, may have introduced a new bug or vulnerability.

     IsoFusion is doing UPS maintenance at the co-location facility.  In theory between 12:01AM and 1AM, however when I was down there tonight to fetch back the unstable server, they were already working on it.  They say it shouldn’t affect service.  But just in case might want to avoid doing anything important between 12:01AM-1AM tonight.