Month: January 2000

We had to reboot our core router mega this…

Thu Jan 13 15:01:45 PST 2000 — We had to reboot our core router mega this afternoon. This accounted for about 5 minutes of downtime. We encountered a bug in the IOS software while trying to shape our network traffic load. Eli and Scott are currently working with Cisco to make sure that it doesn’t happen again. — Eli, Scott, and Kelsey.

Some serious issues at our UUNet upstream…

Sun Jan 9 23:24:11 PST 2000 — Some serious issues at our UUNet upstream router has caused some intermittent connectivity problems – UUNet engineers and Sonic’s staff are working to resolve this, it appears that the core UUNet router at San Jose experienced a failure, and has been repaired. — Eli, Steve.

On Friday the 14th of Jan we will be removing

Fri Jan 7 11:51:51 PST 2000 — On Friday the 14th of Jan we will be removing all traces of statbot from our web servers. If you wish to keep the old stats you should copy the /stats directories from your multihomed website into another directory. Once the stats directory is removed there will be no way of recovering the old information. For those of you who don’t already know, the statbot package was replaced by urchin, which you may access at -Kelsey

It’s the first weekday after Y2K, and we’ve…

Mon Jan 3 19:45:07 PST 2000 — It’s the first weekday after Y2K, and we’ve seen a number of minor cosmetic issues here and elsewhere on the Internet. Typical ones include dates displayed as year ‘100, or as 19100.

Here at, we’ve replaced the shell news reader ‘tin’ with a new version to address a problem where it was offering all groups as new upon startup, which meant you had to say ‘N’ to all groups to get into the program. The new version is 1.4.1, and is a release version that adds some nice new features as well. If you’re interested in continuing to run the old version, you can run ‘tin.old -q’ to get quiet mode so that it won’t offer you new groups. This will mean that you would get notification of legitimate new groups however, so we recommend just running the new version as ‘tin’.

Elm was listing some dates incorrectly, and we’ve updated to a newer version. The new version supports metamail better, and has a number of other new features. However, it does not include closely tied PGP integration, so you’ll need to filter any PGP mail to the command ‘pgp -fm’ if you use PGP. We actually recommend moving away from elm toward mutt, as it’s under much more active development, is faster, and supports larger mailboxes much better.

Our ‘Count.cgi’ counter program was displaying the year as ‘100’ instead of ’00’ for web pages where customers were using the counter to display the current date. We’ve patched the Count.cgi program to resolve this.

Our email invoicing program thought that the year was 2001 instead of 2000 and sent invoices to about 2% of our customers for 12 months longer than their usual billing period. This only affected customers billed by email, not credit card, so no charges were actually made. The software has been fixed, and new invoices have been sent to the affected users already, along with an email note of explanation.

Please keep us posted if you see any other odd behavior that you suspect may be related to the date change. Posting to would be great. -Dane, Eli and Kelsey