Date: Thu, 14 Dec 1995 00:16:50 -0600 (CST) From: Bob Willcox <bob@luke.pmr.com> To: freebsd-current@freefall.FreeBSD.org (freebsd-current) Subject: Re: sups from SUP.FreeBSD.ORG not working well anymore :-( Message-ID: <199512140616.AAA24692@luke.pmr.com> In-Reply-To: <199512140551.XAA24402@luke.pmr.com> from "Bob Willcox" at Dec 13, 95 11:51:21 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Bob Willcox wrote: > > 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?? Hmm, guess I spoke too soon :-( Here is a sample of I'm now getting from sup2.freebsd.org: SUP Upgrade of ports-cad-current at Wed Dec 13 23:58:05 1995 SUP Fileserver supports compression. SUP: Read error on network: Connection reset by peer SUP: Network write timed out SUP: Error reading file list from file server SUP: Upgrade of ports-cad-current aborted at Dec 14 00:07:56 1995 SUP: Network write timed out SUP: Aborted So, I guess it really isn't any better. -- Bob Willcox bob@luke.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512140616.AAA24692>