Clock skew message with NFS and Solaris 8

[Weil, Stefan 3732 SFA-5]

Hello,

maybe this is a bug report for make-3.79.1 (and older
versions).

We use make-3.79.1 on a machine running Solaris 8
with files on a server (also Solaris 8) mounted via NFS.

Both machines use time synchronisation (NTP) and have
nearly the same time (delta t less than 100 ms).

>From time to time, make reports "clock skew" messages
because some file has a modification time in the future.

Inspecting this, I noticed that this file was only
a few milliseconds "in the future". This is quite normal,
because file server and application server (where make
is running) always differ by some milliseconds.
When the application server is behind, every file which
is created will appear with a timestamp in the "future"
because it gets the server's time.

Unfortunately, make on Solaris compares the timestamps
with nanoseconds resolution, so timestamps in the future
are quite normal when files are on a remote filesystem
with a slightly different time.

So, make should accept small clock skews (100 ms or so).
Or this there an other solution?

The problem must also exist on machines with a timestamp
resolution of one second (Linux) when time just jumps to
the next second (remote machine has time t + 1, local machine
still has time t). It just occurs less often (only when a
file is created at the moment when the second increments).

Stefan

PS. Please reply directly, because I did not subscribe
this mailing list.