"Richard B. Gilbert" <rgilber...@comcast.net> writes: >Chris Dew wrote: >>> If like many, you made the mistake of haveing one of the servers be the >>> Local server, you will wait forever. >> >>>> r...@server:~# cat /etc/ntp.conf >>>> server 192.168.1.133 >>>> restrict 192.168.1.133 mask 255.255.255.255 nomodify notrap noquery >> >> I had included the config in a post above. Is the local server added >> as a source by default, as I have not explicitly added it? >> >> Thanks, >> >> Chris.
>I believe you mean "local clock" rather than "local server". >The local clock is NOT a server by default You can configure the local >clock as a "server of last resort" when no other server is reachable. >This will keep your clocks in synchronization and more or less correct >for a few hours but *very few*! Synchronization will last but >correctness will not. >If you really need the correct time you DO NOT want to rely on the local >for any longer than absolutely necessary. Even stronger, you do not want the local clock at all except in the rare case where your machine serves a bunch of other machines and yo u want it to pretend to be up and synchronized even when it is not. The local clock will freewheel whether you have the 127.127.1.0 as a server or not. It does absolutely nothing good for you. _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
