Does anybody knows how to force ntpd - the fully automatic daemon - to start synchronizing time? I presumed that it was designed to do. But it appears it doesn't.
I got several systems with really bad clocks drifting about minute per hour and try to sync them in automatic mode with ntpd. Sometimes ntpd works. But very often it sits in memory and does absolutely nothing. And logs have no error no warning - just heap of messages from start-up.
The only reliable solution I have found is to kill the ntpd and run ntpdate from cron every half hour. That works, though not nice: everybody tells me during last decade that ntpdate is deprecated and shouldn't be used.
From all I have read about ntpd - except its unparsable/unreadable man page - says that my problem should be solvable by ntpd automatically, but even adding undocumented parameters ('iburst' or something like that) to ntpd.conf did not help.
It's not the first time I have such trouble: but on other systems it is less critical, since there clocks are Ok.
Does anybody has any clues? Is it only me who have that problem?