-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anne Wilson wrote: > On Saturday 09 June 2007, Joe Barnett wrote: >> Try running "ntpd -gq" at the end of rc.local to sync the clock. >> Then kick off nptd (with your normal settings) following that. >> > I'm not sure I understand that - what do you mean by the second statement? > I apologize for the confusion. "ntpd -gq" runs the daemon only long enough to sync the clock, then it quits. Think of ntpdate. Why not just use ntpdate? Good question. man ntpd indicates that ntpdate is going to be retired at some point, and that ntpd -q should be used instead. -q seems to stand for quit (as soon as the clock is adjusted). -g tells ntpd not to exit with error if the offset is greater than 1000 seconds. I am not sure why they want to retire ntpdate as it seems a very useful tool. Anyway... Both the stock ntpd and openntpd have features which should bring the clock to good time as soon as they get a good feed from one or more of the servers for which they are configured to use. ntpd -gq, in theory, should not be needed if either ntpd is going to be run as a daemon. That being said, my experience (with both the stock ntpd and openntpd) is that it is best to do a gross adjustment first (whether by ntpd -gq, ntpdate, rdate, etc.) *then* start the daemon. That is why I use two commands to get my ntp stuff going. I hope this helps, thanks, Joe - -- E-mail: joe.barnett@xxxxxxxx Web: http://www.mr72.com/ AOL IM: JoeBarnett Phone: 623.670.1326 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFGastCcGVxc16wzy0RAuaTAJ9ZnSFikl8snwkPmqH0KcA+VR+x1gCYyp0J an2M+rUrF53VP8IoTZrMjQ== =c3F0 -----END PGP SIGNATURE-----
