[Slackdocs] Proofreaders wanted for NTP-HOWTO

Niki Kovacs info at microlinux.fr
Sat Sep 8 21:14:28 CEST 2012

x y a écrit :
> Watch that. If you only sync once, clock drift (or a bad battery causing
> clock drift) on some machines will put them out as much as several
> minutes in 24 hours. Things like network encryption depend on accurate
> time on all machines or they start slowing down and throwing errors and
> not connecting. It can be a big problem to diagnose.

I think there's some misunderstanding here.

1) The initial 'ntpdate' sets the clock right manually, the first time.

2) Once the network is setup as described in the HOWTO, machines are 
*always* in sync. No need for any cronjob, stanza in rc.local or the 
likes. Just point ntp.conf to your server, activate and start rc.ntpd 
and you're done.

You can actually check this out by yourself (which I do when I setup a LAN).

Once everything's configured, run this command on all the clients:

# watch ntpq -p

And then sit back and see how all your clients sync one by one to the 
server... and stay in sync.



Microlinux - Solutions informatiques 100% Linux et logiciels libres
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
Tél. : 04 66 63 10 32

More information about the Slackdocs mailing list