Difference between revisions of "Talk:Network Time Protocol daemon"

From ArchWiki
Jump to: navigation, search
(ntpd -qg)
(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 +
According to [https://bbs.archlinux.org/viewtopic.php?id=150415 this post in the forum], the hwclock daemon is not necessary anymore thanks to systemd, so I'm willing to update this page unless someone have a objection. [[User:Tae|Tae]] ([[User talk:Tae|talk]]) 20:53, 28 December 2012 (UTC)
 +
 
This article has been created after splitting "Network Time Protocol" into this and OpenNTPD as discussed [https://bbs.archlinux.org/viewtopic.php?id=112698 here] -- [[User:Kynikos|Kynikos]] 16:03, 11 February 2011 (EST)
 
This article has been created after splitting "Network Time Protocol" into this and OpenNTPD as discussed [https://bbs.archlinux.org/viewtopic.php?id=112698 here] -- [[User:Kynikos|Kynikos]] 16:03, 11 February 2011 (EST)
  
===<s>Update i18n links</s>===
+
I find this article quite confusing.  My use case is simply that I want to make sure my machine time is sync'd.  I'd suggest that at (or near) the top of the article (before the section on setting up a server) you have info on the canonical approach for this.  The part where this is at the moment is quite bad.
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. -- [[User:Kynikos|Kynikos]] 16:58, 11 February 2011 (EST)
+
 
:[https://wiki.archlinux.org/index.php?title=Network_Time_Protocol_daemon&action=historysubmit&diff=154974&oldid=152801 Fixed], also for the other langauges. -- [[User:Kynikos|Kynikos]] 05:49, 3 September 2011 (EDT)
+
What's the canonical approach daemon or no daemon?
  
===ntpd -qg===
+
Once selected, what's all the warnings about hwclock. Again, canonicalIf hwclock needs to be turned off, just state that, not in RED!  Hope those comments help the article???  Also there are references to rc.conf...shouldn't this be deprecated?  Up front, on top, the systemd approach probably.
Why is {{ic|-g}} required in {{ic|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 {{ic|-g}} from there. - [[User:Corvinus|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  defaultThis 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. [http://lists.ntp.org/pipermail/questions/2011-October/030766.html].
+
:I'm restoring the -g option, but please feel free to continue the discussion if you can find some counter-arguments :)
+
:-- [[User:Kynikos|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).
+
:: -- [[User:Corvinus|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. -- [[User:Jstjohn|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. -- [[User:Corvinus|Corvinus]] 14:47, 16 December 2011 (EST)
+

Revision as of 18:50, 14 February 2013

According to this post in the forum, the hwclock daemon is not necessary anymore thanks to systemd, so I'm willing to update this page unless someone have a objection. Tae (talk) 20:53, 28 December 2012 (UTC)

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

I find this article quite confusing. My use case is simply that I want to make sure my machine time is sync'd. I'd suggest that at (or near) the top of the article (before the section on setting up a server) you have info on the canonical approach for this. The part where this is at the moment is quite bad.

What's the canonical approach daemon or no daemon?

Once selected, what's all the warnings about hwclock. Again, canonical. If hwclock needs to be turned off, just state that, not in RED! Hope those comments help the article??? Also there are references to rc.conf...shouldn't this be deprecated? Up front, on top, the systemd approach probably.