From owner-freebsd-current  Fri Aug  2 16:16:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA09432
          for current-outgoing; Fri, 2 Aug 1996 16:16:56 -0700 (PDT)
Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA09427
          for <freebsd-current@FreeBSD.ORG>; Fri, 2 Aug 1996 16:16:55 -0700 (PDT)
Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id QAA29623; Fri, 2 Aug 1996 16:16:45 -0700
Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.13/8.6.9) id QAA05148; Fri, 2 Aug 1996 16:16:43 -0700
Date: Fri, 2 Aug 1996 16:16:42 -0700 (PDT)
From: Chris Timmons <skynyrd@tahoma.cwu.edu>
To: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
cc: chris@vader.org, freebsd-current@FreeBSD.ORG
Subject: Re: Sup failing for sup.freebsd.org
In-Reply-To: <199608021454.QAA25943@gilberto.physik.rwth-aachen.de>
Message-ID: <Pine.VUL.3.91.960802161602.20431B-100000@tahoma.cwu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



sup5 has been working fine during this period; tried that?

On Fri, 2 Aug 1996, Christoph P. Kukulies wrote:

> > Is anyone else experiencing problems with sup? For the last couple of
> > days I haven't been able to keep up with -CURRENT:
> [...]
> 
> I see this here too. My last working sup was Jul 30th. At the moment my sup
> logs show these timeouts, too.
> 
> 
> > SUP: Can't connect to server for supfilesrv: Operation timed out
> > SUP: Will retry in 416 seconds
> > 
> > I can ping and traceroute to sup.freebsd.org fine:
> 
> [...]
> 
> > Many thanks,
> > 
> > Chris
> > -- 
> > Chris Dabrowski
> > chris@vader.org
> > 
> 
> --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
>