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

From ArchWiki
Jump to: navigation, search
(not sure about "Cannot assign requested address")
 
(102 intermediate revisions by 13 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)
+
= Cannot assign requested address =
 
+
Is this section related to the problem ntpd isn't starting/crashing on systems with kernel option "ipv6.disable=1" enabled? If yes, you can solve it by adding "-4" to your ntpd.config like "restrict -4 127.0.0.1eg." If not, we might add another section?! [[User:T.ask|t.ask]] ([[User talk:T.ask|talk]]) 20:13, 13 December 2017 (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)
 
 
 
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.
 
 
 
I'm removing the the hwclock daemon warning. The forum post linked above, [[Daemons_List]], and {{ic|pgrep hwclock}} or {{ic| ls /usr/lib/systemd/system/}}  on my own system indicate that there is no reason to disable a hwclock daemon. [[User:ChariotOfFire|ChariotOfFire]] ([[User talk:ChariotOfFire|talk]]) 10:37, 19 March 2013 (UTC)
 

Latest revision as of 20:13, 13 December 2017

Cannot assign requested address

Is this section related to the problem ntpd isn't starting/crashing on systems with kernel option "ipv6.disable=1" enabled? If yes, you can solve it by adding "-4" to your ntpd.config like "restrict -4 127.0.0.1eg." If not, we might add another section?! t.ask (talk) 20:13, 13 December 2017 (UTC)