On Sun, 31 Mar 1996 22:52:07 +4200 (CST) 
 rhealey@helios.mn.org (Rob Healey) wrote:

 > 	I haven't been able to sup for a couple of days now.
 > 	
 > 	I can telnet and ftp to sup.netbsd.org just fine, and it's rather fast
 > 	too now that the backbone people are finally fixing routing.
 > 	
 > 	It's like sup.netbsd.org isn't providing sup service anymore?!? What's
 > 	up?

A few days ago, I *did* post that the SUP server had been reconfigured 
... two or three new sets were added, and the server conviguration was 
placed under revision control.

However, since then, I've been getting an awful lot of "time out" 
messages from folks.  These timeouts seem to correspond to the following 
conditions on the SUP server:

netstat -f inet | grep sup
[Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)]
tcp        0  15893  netbsd.supfiled        wipux2.wifo.uni-.1334  ESTABLISHED
tcp       93      0  netbsd.supfiles        Pescadero.DSG.St.3820  CLOSE_WAIT
tcp       39      0  netbsd.supfiles        henric-ppp.zoom..1107  CLOSE_WAIT
tcp       39      0  netbsd.supfiles        jake-6a.aip.real.1084  CLOSE_WAIT
tcp       39      0  netbsd.supfiles        foot.cst.com.au.3119   CLOSE_WAIT
tcp       39      0  netbsd.supfiles        pgoyette.bdt.com.1040  CLOSE_WAIT
tcp       93      0  netbsd.supfiles        henric-ppp.zoom..1032  CLOSE_WAIT
tcp       39      0  netbsd.supfiles        pgoyette.bdt.com.1027  CLOSE_WAIT
tcp       93      0  netbsd.supfiles        rzbsdi01.uni-tri.2930  CLOSE_WAIT
tcp        0      0  netbsd.supfiles        128.204.42.41.1041     ESTABLISHED
netbsd (thorpej) ~ 139% date
Mon Apr  1 08:47:24 PST 1996
netbsd (thorpej) ~ 140%

I have a hard time believing that this is an artifact of adding a few 
sets to the SUP collection.

I simply haven't had time to debug this particular problem further; my 
weekend was quite busy helping a friend move to a new house and getting 
the network insatlled at a VR conference my Real Employer is co-sponsoring.

In the mean time, however, I've restarted the SUP server, and I see now 
that folks are getting through.

Jason R. Thorpe
NetBSD Core Group
<thorpej@NetBSD.ORG>