Re: kernel 2.0.36 - 486 DX2 - clock skew?

H. Peter Anvin (hpa@transmeta.com)
10 Feb 1999 06:49:07 GMT

Followup to: <199902100424.FAA14659@plateau.rug.ac.be>
By author: Immanuel Litzroth <immanuel@plateau.rug.ac.be>
In newsgroup: linux.dev.kernel
>
> >>>>> "Jim" == Jim Woodward <jim@jim.southcom.com.au> writes:
>
> Jim> On Tue, 9 Feb 1999, Alex Buell wrote:
> >> On Wed, 10 Feb 1999, Jim Woodward wrote:
> >>
> >> >
> >> > I was just compiling kernel2.0.36 on my 486 DX2/66 linux
> >> system and > got this message:
> >> >
> >> > make[1]: *** Warning: Clock skew detected. Your build may be
> >> incomplete.
> >>
> >> Not a bug. It's a side effect of using NFS, when your NFS
> >> server's clock is out of sync with the NFS client's
> >> clock. Synchronise both clocks and the message will go away.
>
> Jim> Is there an easy way to sync the client to the server?
>
> Yes, use timed. For synchronization outside your local area network
> you would use ntpd.
> just do timed -M on the servers and
> timed on the clients
> Immanuel
>

ntpd is obsolete, use xntpd. I don't see any reason to use timed over
xntpd at all -- xntpd has a much better synchronization model.

-hpa

-- 
"Linux is a very complete and sophisticated operating system.  There
are, and will be, large numbers of applications available for it."
    -- Paul Maritz, Group Vice President for Platforms And Applications,
       Microsoft Corporation [Reference at: http://www.kernel.org/~hpa/ms.html]


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/