From Fedora Project Wiki

No edit summary
No edit summary
Line 4: Line 4:
Agreed.  I had no idea I was already running an NTP client.  It seems it doesn't work correctly, since I subsequently installed ntpd.   
Agreed.  I had no idea I was already running an NTP client.  It seems it doesn't work correctly, since I subsequently installed ntpd.   
Can we please stop this strange naming of system utilities.  chrony is so similar to chron, that I assumed it was related.  It never occured to me it might be a repalcement NTP daemon.
Can we please stop this strange naming of system utilities.  chrony is so similar to chron, that I assumed it was related.  It never occured to me it might be a repalcement NTP daemon.
 
...redacted...
Furthermore, if chronyd is the new ntpd, why does this page http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html refer to ntpd, and not mention chronyd at all !

Revision as of 08:35, 5 February 2015

Any reason we don't call this just ntp-ng? It's getting harder to figure out what half these daemon projects are called. NTP is what it spells. 'Chrony' does not sound like time to me.

--Smitty (talk) 08:33, 5 February 2015 (UTC) Agreed. I had no idea I was already running an NTP client. It seems it doesn't work correctly, since I subsequently installed ntpd. Can we please stop this strange naming of system utilities. chrony is so similar to chron, that I assumed it was related. It never occured to me it might be a repalcement NTP daemon. ...redacted...

Retrieved from "https://fedoraproject.org/w/index.php?title=Talk:Features/ChronyDefaultNTP&oldid=402733"