From owner-freebsd-current  Wed Dec 13 07:05:33 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA18759
          for current-outgoing; Wed, 13 Dec 1995 07:05:33 -0800 (PST)
Received: from luke.pmr.com (luke.pmr.com [199.98.84.132])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA18748
          for <freebsd-current@freefall.FreeBSD.org>; Wed, 13 Dec 1995 07:05:24 -0800 (PST)
Received: (from bob@localhost) by luke.pmr.com (8.6.12/8.6.9) id JAA22518 for freebsd-current@freefall.cdrom.com; Wed, 13 Dec 1995 09:05:21 -0600
From: Bob Willcox <bob@luke.pmr.com>
Message-Id: <199512131505.JAA22518@luke.pmr.com>
Subject: sups from SUP.FreeBSD.ORG not working well anymore :-(
To: freebsd-current@freefall.FreeBSD.org (freebsd-current)
Date: Wed, 13 Dec 1995 09:05:21 -0600 (CST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

I have noticed that lately (last 3-4 days or so) that my attempts at supping
from SUP.FreeBSD.ORG have not been to reliable.  I keep geting stuff like:

SUP: Will retry in 333 seconds
SUP: Read error on network: Connection reset by peer
SUP: Premature EOF on network input
SUP: Network write timed out
SUP: Error receiving file from file server
SUP: SUP: Upgrade of ports-plan9-current aborted at Dec 13 08:28:24 1995
Network write timed out
SUP: Aborted
SUP: Read error on network: Connection reset by peer
SUP: Premature EOF on network input
SUP: Network write timed out
SUP: Error receiving file from file server
SUP: Upgrade of ports-www-current aborted at Dec 13 08:38:43 1995
SUP: Network write timed out
SUP: Aborted
SUP: Will retry in 99 seconds
SUP: Will retry in 162 seconds
SUP: Will retry in 367 seconds
SUP: Will retry in 552 seconds

This goes on for hours.  Anybody got clue?

Thanks,
-- 
Bob Willcox
bob@luke.pmr.com (or obiwan%bob@uunet.uu.net)
Austin, TX