I've bumped into something which is called "NTP step tickers" and read about it in this article, but I'm not sure if it's required in a domain which includes local NTP servers.
It seems like it replaces /etc/ntp.conf
configuration file with /etc/ntp/step-tickers
configuration file or is it supposed to be there in addition to the /etc/ntp.conf
file?
Can anyone please shed some light on this matter?
Best Answer
NTPd famously, by default, won't adjust the time if it's more than 1000s out, presuming as it does that there's a systemic problem with which it shouldn't get involved. This from
man ntpd
:One problem is that BIOS clocks in the UK are often an hour out, because of misunderstandings about whether the BIOS is in UTC or summer time. I imagine the problem gets worse as your longitude from Greenwich increases.
So there is also a command
ntpdate
, which wrenches the system clock into alignment with an NTP server, in an unsubtle manner that tends to upset a lot of running services. I believe it predates the addition of the-g
flag to ntpd.Thus, for old-timers like myself, the full startup protocol for
ntpd
involves the use ofntpdate
to forcibly sync the clock - on the basis that that's safest to do when the system starts up - followed by startingntpd
to keep it there./etc/ntp/step-tickers
controls which server is used to do thentpdate
. I usually list one of myntp.conf
servers in there.To further confuse the matter, the
ntpdate
startup script on CentOS6 will look inntp.conf
for a startup ticker if one isn't listed instep-tickers
. So whilst it is certainly good practice to make sure thatntpd
won't be left high and dry (trying to sync a system clock that's too far out), between modern startup scripts and the-g
flag tontpd
,step-tickers
really is a historical relic, with no necessary function in a modern distro. But I'm a historical relic, too, and so I continue to use it.