Subject: sup problems for current-domestic?
To: None <current-users@NetBSD.ORG>
From: Paul Goyette <paul@pgoyette.bdt.com>
List: current-users
Date: 12/24/1995 10:31:26
Is anyone else having problems with supping the current-domestic 
collection?  

Every time I try, it gets as far as kdb_init/kdb_init.c and then just 
hangs up.  I've gone so far as to run a tcpdump on the sup session, and 
all it shows is that the server (sup.netbsd.org) continues to send the 
same packet several times (usually 6 or so) while the client (me) just 
sits there - no acknowledgement.  After waiting around for several (from 
5 to 10) minutes, the client then aborts the tcp session, and sup reports 
the following error messages:

SUP Receiving file src/domestic/usr.sbin/kdb_init/kdb_init.c
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 current-security aborted at Dec 24 10:29:39 1995
SUP: Network write timed out
SUP: Aborted

I am able to sup all the other collections, including current-allsrc, 
so I'm at a complete loss to understand why it stops in the same place 
_every_ time in current-domestic.  Any ideas, anyone?