I feel pretty stupid; this is right up there with my message about the
sparc 5 beeping when it was actually an old pager going off that I thought
had been disconnected. This problem was due to a mismatch in time between
the NFS client and the NFS server. Syncing the time fixed the problem.
NOTE: this also fixed serious hanging problems in Pine (see my next
summary). I had considered NFS being the culprit, but I ASSumed that the
client set the date on the file (which was wrong, because it was probably
a kernel function, and in that case, the kernel on the NFS server would
handle it.) The basis of this assumtption was based on the fact that a
client can set the uid of the file, even if the server isn't aware of it.
I'm also not completely guilty for this time mismatch. I have a cisco
setup as a stratum-2 NTP server, and I was planning on syncing the sparcs'
clocks on it over xntpd when I found the time. My original message follows
Thank you to:
William L. Hamlin
Niall O Broin
Syed Zaeem Hosain
Carsten B. Knudsen
... and, of course, Mom.
My original Message follows.
---------- Forwarded message ----------
Date: Tue, 5 May 1998 10:48:31 -0400 (EDT)
From: Admin Staff <email@example.com>
To: Sun Managers <firstname.lastname@example.org>
Subject: Bizarre File Date Problem
Followup-To: Admin Staff <email@example.com>
To add to my Solaris 2.6 problems (:-))
I have an ultra that's creating files with timestamps that are about 10
minutes in the future.
Tue May 5 10:47:40 EDT 1998
[titan][pts/1]% touch test
[titan][pts/1]% /usr/ucb/ls -l test
-rw------- 1 admin1 0 May 5 10:55 test
Has anyone had this problem?
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:39 CDT