From owner-freebsd-current Wed Nov 4 11:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13499 for freebsd-current-outgoing; Wed, 4 Nov 1998 11:05:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13469 for ; Wed, 4 Nov 1998 11:05:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA12713; Wed, 4 Nov 1998 11:05:38 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Jeroen Ruigrok/Asmodai cc: John Hay , current@FreeBSD.ORG, mark@grondar.za (Mark Murray) Subject: Re: cvsup server down? In-reply-to: Your message of "Wed, 04 Nov 1998 19:59:25 +0100." Date: Wed, 04 Nov 1998 11:05:37 -0800 Message-ID: <12710.910206337@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we get freebsd-current@freebsd.org back to being a relatively low-traffic mailing list, folks? We can chat about lightning strikes over in -chat, you know! :-) Thanks... - Jordan > On 04-Nov-98 John Hay wrote: > >> Jeroen Ruigrok/Asmodai wrote: > >> > Hi, > >> > > >> > just to get this verified: > >> > > >> > cvsup.internat.freebsd.org down for maintnance? > >> > >> Keep trying, and also try cvsup2.internet.freebsd.org; these are busy > >> machines. > > > > Well this time it wasn't because it was busy. Lightning knocked out our > > link and it took a while for Telkom to fix it. :-/ > > Icky! > > No UPS's ? > > Or did it hit the more central stuff directly? > > --- > Jeroen Ruigrok van der Werven/Asmodai > asmodai(at)wxs.nl > Junior Network/Security Specialist > FreeBSD & picoBSD: The Power to Serve... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message