Talk:Network Time Protocol daemon

From ArchWiki
Revision as of 19:47, 16 December 2011 by Corvinus (Talk | contribs) (ntpd -qg)

Jump to: navigation, search

This article has been created after splitting "Network Time Protocol" into this and OpenNTPD as discussed here -- Kynikos 16:03, 11 February 2011 (EST)

Update i18n links

Note that the i18n links still point to "Network Time Protocol" instead of "Network Time Protocol daemon": this should be changed if also the other wikis split the original article like this. -- Kynikos 16:58, 11 February 2011 (EST)

Fixed, also for the other langauges. -- Kynikos 05:49, 3 September 2011 (EDT)

ntpd -qg

Why is -g required in ntpd -qg in Using without daemon? It allows to adjust time by more than 15 min without a warning, which seems like a very specialized need. If there isn't something I don't know, I'd like to remove -g from there. - Corvinus 10:28, 3 December 2011 (EST)

Sorry for the delay of this answer. From man ntpd: Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option (-g) allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log.
Not only the -g option causes no harm, but since you're running ntpd only at boot time, you can't predict whether the clock is off by more than 15 minutes or not, and if it is, without the -g option it won't be adjusted.
Googling it just a bit gives you some references, e.g. [1].
I'm restoring the -g option, but please feel free to continue the discussion if you can find some counter-arguments :)
-- Kynikos 16:17, 15 December 2011 (EST)
I disagree, -g would cause harm, because if clock is off by more than 15 min it means one of the following:
  • you run ntpd too rarely (must be several years perhaps),
  • your clock chip is hosed (no need setting it up),
  • some timezone/etc settings are incorrect and ntpd tries to do the wrong thing.
In either case, it's better to leave the clock as is and alert user (that's why this panic threshold is present in first place).
-- Corvinus 11:02, 16 December 2011 (EST)
But Kynikos stated that it only does the adjustment once, which makes argument #2 mostly a non-issue (unless he meant once per boot...). And #1 should be mostly a non-issue, especially because the wiki highly discourages users from not running ntpd in daemon mode. -- Jstjohn 13:18, 16 December 2011 (EST)
If they're non-issues, you don't need -g. If they are issues, you don't need -g either, since in this rare case it's better to be notified instead. -- Corvinus 14:47, 16 December 2011 (EST)