From owner-freebsd-current  Wed Dec 13 21:51:28 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA07505
          for current-outgoing; Wed, 13 Dec 1995 21:51:28 -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 VAA07494
          Wed, 13 Dec 1995 21:51:21 -0800 (PST)
Received: (from bob@localhost) by luke.pmr.com (8.6.12/8.6.9) id XAA24402; Wed, 13 Dec 1995 23:51:21 -0600
From: Bob Willcox <bob@luke.pmr.com>
Message-Id: <199512140551.XAA24402@luke.pmr.com>
Subject: Re: sups from SUP.FreeBSD.ORG not working well anymore :-(
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Wed, 13 Dec 1995 23:51:21 -0600 (CST)
Cc: freebsd-current@freefall.freebsd.org
In-Reply-To: <199512131625.IAA28481@freefall.freebsd.org> from "Justin T. Gibbs" at Dec 13, 95 08:25:43 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

Justin T. Gibbs wrote:
> 
> Dima has also reported this, but I can't get it to happen here.
> What version of the kernel are you running?  What version of SUP?
> Is it only the ports collections?

I am running 2.1-stable and sup 8.26.

> 
> I did make some modifications to sup, but they should only have affected
> how the scan files are found/generated.  Of course, SUP is such a festering
> pile of globals and poor design that my changes may have had other
> ramifications, but I wouldn't have expected newtwork read/write failures.
> Anyone who has the time, feel free to review the patch-ab that is in
> our current port.
> 

I changed from sup.freebsd.org to sup2.freebsd.org (per Richard
Wackerbarth's suggestion) and it seems to be running now.  Perhaps
it is getting lost when trying to recover from an overloaded server??

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