[2631] in Athena Bugs
Re: missing directory (actually: clock problems!)
daemon@ATHENA.MIT.EDU (Jerry Saltzer)
Mon Jul 24 18:47:29 1989
From: saltzer@src.dec.com (Jerry Saltzer)
Date: 24 Jul 1989 1546-PDT (Monday)
To: geer@ATHENA.MIT.EDU, bugs@ATHENA.MIT.EDU
Date: 24 Jul 1989 1133-PDT (Monday)
original-To: Jeffrey I. Schiller <jis@athena.mit.edu>
original-Cc: bugs, geer
Subject: Re: missing directory (actually: clock problems!)
In-Reply-To: Your message of Sun, 23 Jul 89 21:07:01 -0400
<8907240107.AA16237@OSIRIS.MIT.EDU>
> I just checked and the directory /mit/Saltzer does indeed exist
> on Eurydice and is populated. I do know that there were disk problems
> with Eurydice earlier this week and that dkk (Dave Krikorian) was
> dealing with the problem. I don't know the resolution but *if* we
> got a new disk you may well have attempted to attach your locker
> while a restore was in progress!
Thanks for checking. I looked again, the directory is still "missing",
so I looked harder. It turns out that the problem is elsewhere.
This time, I tried to attach athenadoc and got a different message:
that my Kerberos ticket has an out-of-bound time. Thanks to the
extra RVD pack with the name "Saltzer", I never saw that error message
for my own directory, so didn't realize that might be what the trouble
is. And the error message from /etc/mount ("no such file or
directory") was even more misleading.
So now I have a different, probably more serious problem--it looks
like my clock is being screwed around with by timed. You may recall
that when I first installed 6.2A I reported that it set my clock
three minutes ahead of real time. (I don't recall hearing any
response to that bug report.)
Date now tells me that the time on my RT is Mon Jul 24 14:33:50 EDT,
while a few seconds later on allspice date tells me that the time
is Mon Jul 24 13:34:22 EDT. Allspice is right; the RT's clock is
running EXACTLY one hour ahead.
/usr/adm/messages tells me that on July 13 at 11:02:15, the
"date was changed by spiff from 10:06:08." In other words,
the magic new time software pushed the clock ahead an hour. There
are about a dozen time-adjustment messages in the log, mostly
showing a few seconds change, but that one certainly looks wierd.
Is there a possibility that an insecure time-change protocol is
being screwed around with by hackers?
I set the clock back an hour and now I can attach my directory.
The clock on my RT has previously run for months (as long as 123
days) without the clock drifting more than a few seconds. If
you don't mind, I'm inclined to leave timed off.
Jerry
Jun 29 09:02:10 NE43-513-2 timed[677]: date changed by spiff from: Thu Jun 29 09:02:08 1989
Jun 29 09:15:38 NE43-513-2 timed[677]: date changed by spiff from: Thu Jun 29 09:15:38 1989
Jun 29 10:04:41 NE43-513-2 timed[677]: date changed by spiff from: Thu Jun 29 10:04:40 1989
Jun 30 13:20:25 NE43-513-2 timed[677]: date changed by spiff from: Fri Jun 30 13:20:23 1989
Jul 7 11:06:25 NE43-513-2 timed[677]: date changed by spiff from: Fri Jul 7 11:06:27 1989
Jul 8 19:02:19 NE43-513-2 timed[677]: date changed by spiff from: Sat Jul 8 19:02:19 1989
Jul 10 11:50:29 NE43-513-2 timed[677]: date changed by spiff from: Mon Jul 10 11:50:29 1989
Jul 10 16:43:53 NE43-513-2 timed[677]: date changed by spiff from: Mon Jul 10 16:43:52 1989
Jul 13 11:02:15 NE43-513-2 timed[677]: date changed by spiff from: Thu Jul 13 10:06:08 1989
Jul 15 19:19:06 NE43-513-2 timed[677]: date changed by spiff from: Sat Jul 15 19:19:04 1989
------- End of Forwarded Message
