🚀 go-pugleaf

We've had a bunch of problems here this past week that have made tomcat not
be online very much:

(1) A fault developed in the motherboard on the 386-25 that was in use.
The effect was memory parity errors with a mean-time-to-crash measured
in minutes. No simple fix worked. The machine has gone into the 'puter
hospital to make it well.

(2) A spare 386-20 was put online using the hard disk and etherenet card
from the old host. It also ended up being flaky, apparently due to something
conflicting between the VGA and the ethernet board. Memory addresses and
interrupts were diddled with little success. Finally (before it went into
the shop on Friday), I swapped the VGA boards between the "old" tomcat host
and the temporary box and it seemed to fix things.

(3) Starting Friday until this morning, for some unexplained reason, the
NASA/GSFC LAN had problems. We were fully connected within our building
(which includes the host that is our facility's nameserver), but the
connection was broken to the other buildings (which includes the bank
of routers used to connect the Center to the world).

(4) Somehow between WD3Q and me, the master (call sign)-to-(Email address)
ALIAS file got clobbered. I reconstructed it with a backup I had at home.

I'm not certain that all the problems are fixed yet. N4HY sez I have a big
black cloud hanging over my head! Patience on your part is advised.

Tom