Date: Fri, 15 Dec 1995 10:18:07 +0100 (MET) From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: nate@rocky.sri.MT.net (Nate Williams) Cc: bob@luke.pmr.com, freebsd-current@freefall.freebsd.org Subject: Re: sups from SUP.FreeBSD.ORG not working well anymore :-( Message-ID: <199512150918.KAA02902@gilberto.physik.rwth-aachen.de> In-Reply-To: <199512142119.OAA14491@rocky.sri.MT.net> from "Nate Williams" at Dec 14, 95 02:19:24 pm
next in thread | previous in thread | raw e-mail | index | archive | help
>
> Bob Willcox writes:
> > Well, sup has gone from bad to worse for me. I can no longer get it to
> > work at all! Using sup.freebsd.org I am now getting:
> >
> > SUP 8.26 (4.3 BSD) for file stable-supfile at Dec 14 09:14:46
> > SUP: Can't find host entry for sup.FreeBSD.org
> > SUP: Will retry in 73 seconds
> > SUP: Can't find host entry for sup.FreeBSD.org
>
> This means your host can't resolve sup.FreeBSD.org, and it's now sup's
not
> fault.
>
> > and with sup2.freebsd.org its simply:
> >
> > SUP 8.26 (4.3 BSD) for file stable-supfile at Dec 14 09:27:58
> > SUP: Can't connect to server for supfilesrv: Operation timed out
>
> This means it can't make a network connection to sup2.FreeBSD.org, which
> is a network problem and again not sup's fault.
>
> The Internet in and around the Bay area is having *lots* of problems due
> to the recent storms, so I wouldn't expect everything to work for
> awhile.
Maybe it's a good idea to insert freefall's IP address in the sup file
to make sup more robust against outage of other network resources.
>
>
>
> Nate
>
--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512150918.KAA02902>