Subject: Re: sup-server brokenness...
To: Mike Long <email@example.com>
From: John F. Woods <firstname.lastname@example.org>
Date: 10/10/1995 16:00:51
> 1) sup.netbsd.org (aka netbsd.warped.com) is always busy. Has
> *anyone* been able to sup successfully from this machine?
Yes. It took a long time, but sup is good at waiting, so I let it do it.
I assume that netbsd.warped.com is being hammered by several dozen people
trying to sup, and since its file dates are all different from sun-lamp's
(presumably sun-lamp's crash made it impossible to restore the original
file times), those lucky few who succeed get to watch sup take several hours
to work. (netbsd.warped.com also appeared to crash once during a sup, which
didn't help.) At roughly three successes per day per allowed simultaneous
connection, it'll take a long time to empty a queue of several dozen...
> Problems like this one probably do more to drive users away than
> install tools, politics, or anything else.
It's real hard to recover from a disk crash on an active system like a sup
server. It's even harder when it doesn't have a paid attendant to do daily
Perhaps individuals should refrain from running sup until some of the mirrors
have caught up? (And those mirrors that are using "sun-lamp.cs.cmu.edu"
instead of "sup.netbsd.org" should be updated pronto.)
Once the mirrors catch up, what are the issues involved in having users
alternate between different sup servers? I.e. would it be practical to
spread the load by having "sup.netbsd.org" resolve to several shuffled
addresses? (Of course, then the mirrors have to use "sup-master.netbsd.org"
or something like that.)