Re: a coreutils release is imminent

[Matthew Woehlke]

Jim Meyering wrote:
> Matthew Woehlke <address@hidden> wrote:
> > ...yike! Hmm... ok, *now* I see the problem. It turns out this box's
> > clock is WAAAAY off (about 21 minutes). So I guess this can be ignored.
>
> Yep.  As you probably noticed, that's what the failing test suggested:
>
>   *** This test has just failed.  That can happen when the test is run in an
>   *** NFS-mounted directory on a system whose clock is not well synchronized
>   *** with that of the NFS server.  If you think that is the reason, set the
>   *** environment variable SLEEP_SECONDS to some number of seconds larger than
>   *** the default of $DEFAULT_SLEEP_SECONDS and rerun the test.

Right. I was just surprised because OSF is being an oddball here; on 
Solaris and Linux, 'touch a' results in 'a's time stamp being current as 
compared to the *server's* clock, not the host's clock. I'm used to 
leveraging that to /find out/ if the host and the NFS server disagree. 
In this case that didn't work, and caused me to think that they were in 
sync when in fact they aren't. (Guess I'll have to try to teach myself 
to stop doing that :-).)

--
Matthew
Congratulations! You've won a free trip to the future! All you have to 
do to claim your prize is wait five minutes...