-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-10-04 at 09:54 -0500, Peter Van Lone wrote:
On 10/4/06, Carlos E. R. wrote:
Or in this case, start a cron job running ntpdate periodically - I mean every fifteen minutes or so. If at that moment there is a network, it will sync. There is little or no point in running ntp if there is no _permanent_ network connection.
a cron job sounds like another good way to go. I heartily disagree with your judgement in the last line ... it seems to me patently ridiculous that my laptop has to have inaccurate time just because it is not permantly network connected -- my computer is my watch basically.
It seems like a simple, normal, regular request. It seems like it should not be so hard to do. Now, I have a couple different methods for doing it, so once I figure out how to do either one, I'm set.
Er... you misinterpreted me. First, you can keep accurate time by using ntpdate only once a day: I did it that way for years, and the error was a second or two at the end of day: the same as a hand watch. Programming a query interval of fifteen minutes is just for the purpose of ensuring that at least some of the queries fall inside a connected window. Second, I said: «there is little or no point in running ntpd if there is no _permanent_ network connection». This is simply a technical requirement of the ntp daemon, not a judgment. It has to query the time at unknown moments (unknown for us), and having no network when it needs it means it will not work. Notice that it keeps the clock accurate up to about 0.01 S. In other words, ntpd is designed for machines with permanent network connections. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFJAVXtTMYHG2NR9URAtrVAKCNihIX53UEpXFDEV6/k6uV0LSYuwCfQdmM 3lIQi+T4U1yJTREiFIlIRI4= =RjYW -----END PGP SIGNATURE-----