On Mon, May 03, 2010 at 10:20:56PM -0600, Mr Ritter wrote: > > If your clock gets too far out of sync (maybe from a reboot, if you aren't > syncing the hardware clock from system) ntpd will not sync your clock > anymore. ntp-client is usually used to sync your clock regardless of offset > and get it current before ntpd starts.
Although in my experience, specifying iburst in the ntp.conf seems to be just as effective as using ntp-client in this case. I usually restrict my use of ntp-client to situations where I don't need a particular level of clock accuracy and where it would be more trouble than it's worth to run the ntp daemon. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868 /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
