From owner-freebsd-current Tue May 30 03:34:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA24087 for current-outgoing; Tue, 30 May 1995 03:34:12 -0700 Received: from aries.ai.net (ai.net [198.69.35.206]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA24063 for ; Tue, 30 May 1995 03:34:03 -0700 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id GAA16718; Tue, 30 May 1995 06:30:34 -0400 Date: Tue, 30 May 1995 06:30:34 -0400 (EDT) From: Network Coordinator To: "Rodney W. Grimes" cc: Wes Santee , freebsd-current@FreeBSD.org Subject: Re: SUP server down? In-Reply-To: <199505300420.VAA02429@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 29 May 1995, Rodney W. Grimes wrote: > > > > Did I miss something? Looks like the SUP server has been down pretty > > much all day. If this was a 'scheduled outage' then I guess everybody > > gets to laugh at me and I'll go back and read all my e-mail. If not, > > anybody know what the problem is? > > You missed something, have you been reading your -current and -commit > mailling lists???? > having just read the relevant message -- two things, it came about 10 hours after I noticed sup was down. That is not a big deal. I'm not complaining, but it would be nice [for those of us who skim the subject lines of messages with pine] if something like "SUP DOWN" was in the title. Then again, you could just call me lazy and that would also work. -Jerry.