Eric wrote:
> As I said, we do use NTP to keep our machines in synchronization, every
> hour. ...
If you are doing something other than running ntpd as a daemon, you are
likely not keeping your clocks sync's well enough to keep NFS timestamps
happy.
H
As I said, we do use NTP to keep our machines in synchronization, every
hour. However, there's no time client that will keep everything aligned
up to the nanosecond level, which is what ext4 timestamps are in.
Besides, any amount of network lag is going to introduce small errors in
this anywa
Bob Friesenhahn writes:
> Usually the solution to this is to install and run ntp (Network Time
> Protocol, as offered by 'xntp') on the machines on your network.
Is that really a solution? Running ntp makes it a lot more _likely_
that machines will appear to be synchronized to a high degree of
p
On Wed, 12 Jan 2011, Eric Reischer wrote:
I recently upgraded our NFS fileserver to an ext4 filesystem, and since then
we've been having clock skew warnings from make (3.81). Because the ext3
filesystem that was previously running on the NFS server didn't support
high-precision timestamps, we
[adding bug-make, replies can drop automake]
On 01/12/2011 03:08 PM, Eric Reischer wrote:
> I recently upgraded our NFS fileserver to an ext4 filesystem, and since
> then we've been having clock skew warnings from make (3.81). Because
> the ext3 filesystem that was previously running on the NFS s
I recently upgraded our NFS fileserver to an ext4 filesystem, and since
then we've been having clock skew warnings from make (3.81). Because
the ext3 filesystem that was previously running on the NFS server didn't
support high-precision timestamps, we didn't have clock skew warnings
because an
