[comp.protocols.tcp-ip] Clockwatchers beware

louie@TRANTOR.UMD.EDU (Louis A. Mamakos) (09/16/87)

Folks,
	The WWVB clock attached to UMD1.UMD.EDU aka WWVB.UMD.EDU is not
currently usable, as the disk drive on that host is very unhappy.  If you
use the clock services of this clock with UDP/NTP or UDP/TIME, you'll be
out of luck for a day or two.

louie

Mills@UDEL.EDU.UUCP (09/18/87)

Louie,

Why don't you reterminate the clock on the NSF fuzzball, which would make
it a functional duplicate of the NCAR machine?

Dave

louie@TRANTOR.UMD.EDU (Louis A. Mamakos) (09/18/87)

Dave,
	The clock and machine are feeling much better now, thank you.  We
would have done something like this, but the machines are in two different
rooms.  I decided that I would be faster to replace the disk driver than move
the clock and reroute various wires, cables and other snakes.

Let me know thinks don't seem back to normal.

louie

Mills@UDEL.EDU (09/19/87)

Louie,

Things do seem better, although last night (before you redrived?) I noticed
a few timewarps between umd1 and udel1. Note that the Linkabit clock has
frozen again. They won't fix it, since that costs money, so Woody is
reduced to conking it with a wrench, which sometimes even wakes it up.

Dave