[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bogus Modified in Future Message

From: Mark D. Baushke
Subject: Re: Bogus Modified in Future Message
Date: Wed, 28 Jan 2004 13:36:26 -0800

Hash: SHA1

Rod Macpherson <address@hidden> writes:

> Have a bunch of files that were added today at 11:24 AM PST and the date
> on the repository images concurs. Checking out those files generate a
> "Warning: modified in future" and a check of the log indicates the files

Which command is generating this warning? (Is it make?)

When soliciting help, it is often useful to provide information like the
exact versions of cvs you are using and the exact output with the errors
and warnings you are seeing, it is hard to help you remotely diagnose
problems when you paraphrase warning messages or do not tell us when
you see them.

> were added at 7:24 PM PST. The client and server clocks look fine so
> what could account for the log being off by 8 hours?

Eight hours is the difference between UTC and PST. The repository should
always be keeping its modified timestamps in UTC rather than PST. I
would expect to see a file checked in at 11:24AM PST time to show a
repository time of 19:24 UTC (aka 7:24PM PST). So, everything looks fine
- From that point of view.

> The archive files themselves show they were last updated at 11:24 AM
> PST so there must be something wacky going on with CVS. Any ideas?

My best guess is that you want to look for an NFS filesystem in the
system somewhere that has a different clock for the time on the server
of that filesystem. When you do a 'cvs update' the server sets the time
on the file to the current time of the checkout and if it is an NFS
filesystem, that means the time presently on the NFS server rather than
the NFS client.

> This is not the first time this has happened and it has happened on
> various machines.
        Good luck,
        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]