On 31/10/06 04:46, Carlos E. R. wrote:
ntp daemon only checks at certain intervals for a time server. Which ntp configuration file could I edit to shorten/lengthen the time between the ntp checks? The last check was at 07h29 and the time now is 08h24 and it hasn't checked inbetween.
No, that's the wrong conclussion. The fact that the daemon doesn't log anything doesn't mean that it hasn't checked the time in the interval. It may have done it hundreds of times for all you know. The stuff that does go into the ntp logfile is actually pretty spartan when it comes to trying to determine what is happening with a particular server, unless one is willing to do a fair bit of digging (as I noted in my tome replying to Hylton's first post). Better would be to use the "statistics" and "filegen" directives, but I have only got those to work once, and I can't recall what made it work. It worked for awhile, then stopped after a re-install of the entire OS (when I changed hard drives). I'm sure I am still using identical directives, but I've never seen any statistics files show up since. The resultant files were definitely full of useful information when any problems arose connecting with a particular server. If anyone has a working statistics/filegen combination, I would definitely like to see the lines.
And you can not modify when ntp sees fit to check the time.
minpoll/maxpoll
If this configuration is not available, what command could I issue to initiate an ntp time check against the internet ntp servers ie after I have enabled the net connection?
Do not use the ntp daemon unless your connection is permanent.
ntpd -q does the same thing as ntpdate. See also my second note to John Anderson.