🚀 go-pugleaf

In article <+MU!YM=_L@linac.fnal.gov> matt@severian.chi.il.us (Matt Crawford) writes:
>I don't believe the recent problems have been due to any equipment
>other than clout itself (or the ethernet segment clout is connected
>to).

There has been quite a bit of work done on the same segment that clout is
connected to.  There are several NeXT machines on that cable, and they are
being set up and re-configured.  As a result of this normal, necessary
maintainance (at least until the NeXTs are set up to the satisfaction of
all concerned :-) the ethernet segment will experience some disruption.
Not much, though, and the NeXTs are pretty much finished...

>The problem is not on the modem pool or the gandalf, I'm sure.

Forgive me if this sounds bad, but, if you don't use the modem pool or the
tipserver how can you say there isn't a problem there?  The fact that they
aren't the only problem point doesn't mean that they aren't problem
points.

I can say quite unequivocally that the Gandalf is having problems.  On a
fairly frequent basis it refuses to recognize a connection.  The modem
will connect and then nothing, no ENTER CLASS prompt.  This isn't
anywhere near clout, or clout's ethernet segment.

The tipserver seems to have been upgraded recently, and possibly the
installation of whatever provided for it's recent enhancements caused some
flakeyness.  I really don't know, I do know that frequently problems have
shown up well before a connection comes near it.

I am sure the people at the University are aware of the problem.  They
will fix it when they can.  Till then, let's try to put up with any minor
awkwardness as quietly and politly as possible.

Those who find little glitches like this too much to tolerate, I am sure
you will be able to get the consistency of service you desire from such
places as UUNET.  And if things broke then, well any complaints would be
quite justified.
--
Russell Rezaian			|  rrezaian@austral.chi.il.us
  rrezaian@clout.chi.il.us	|  rrezaian@zed.chi.il.us