(Created page with "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 ...") |
No edit summary |
||
Line 1: | Line 1: | ||
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. | 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. | ||
--[[User:Smitty|Smitty]] ([[User talk:Smitty|talk]]) 08:25, 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. |
Revision as of 08:25, 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:25, 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.