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

From ArchWiki
Jump to: navigation, search
(Syncing at boot: Close old discussion.)
(tidy up, see Help:Talk)
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
==<s>Creation history</s>==
 
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> Syncing at boot </s> ==
+
==hwclock daemon==
I'm wondering if it's ok to mention {{ic|{ ntpd -qg; hwclock -w; } }} in [[Network Time Protocol daemon#Synchronize once at boot time]] as the main method and using the hwclock daemon only as an alternative, although the latter is an official daemon provided by initscripts.
+
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)
  
And in any case, the two methods don't seem equivalent, in fact the hwclock daemon just runs {{ic|hwclock --adjust}} at shutdown.
+
: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)
  
This discussion is also related to [[Talk:Time#hwclock daemon]].
+
==Canonical usage==
 +
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.
  
-- [[User:Kynikos|Kynikos]] 11:03, 20 January 2012 (EST)
+
What's the canonical approach daemon or no daemon?
:I think it should be first written without hwclock (as it should be for default config), and then noted that you should check if hwclock is launched, not the other way around like it is now. -- [[User:Corvinus|Corvinus]] 00:42, 21 January 2012 (EST)
+
 
::I've tried to reword the section a bit in that direction. -- [[User:Kynikos|Kynikos]] 08:32, 21 January 2012 (EST)
+
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.
:::Corvinus, I've decided to partly revert one of your recent edits: [https://wiki.archlinux.org/index.php?title=Network_Time_Protocol_daemon&curid=10908&diff=179719&oldid=179586]. Read the explanation I've added in the edit summary and if you don't agree we can of course discuss that here :) -- [[User:Kynikos|Kynikos]] 12:46, 22 January 2012 (EST)
+
::::Alright, you're correct. But what I wanted is to have a clear link at the top of article about how to set time just now. It's sad if that's not possible with current layout. -- [[User:Corvinus|Corvinus]] 02:57, 23 January 2012 (EST)
+
:::::I see, you have a point too indeed... However the name of the main section, "Using without daemon", may be enough to arouse the curiosity of those looking for a way to synchronize just once. Also the fact that the section is placed before the one about using the daemon should help. However there's surely room for improvement, and ideas are welcome! -- [[User:Kynikos|Kynikos]] 07:48, 23 January 2012 (EST)
+

Revision as of 10:48, 13 April 2013

Creation history

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

hwclock daemon

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)

I'm removing the the hwclock daemon warning. The forum post linked above, Daemons_List, and pgrep hwclock or ls /usr/lib/systemd/system/ on my own system indicate that there is no reason to disable a hwclock daemon. ChariotOfFire (talk) 10:37, 19 March 2013 (UTC)

Canonical usage

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.