No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| 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: | --[[User:Smitty|Smitty]] ([[User talk: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. | 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 | Can we please stop this strange naming of system utilities. chrony is so similar to chron, that I assumed it was related. It never occurred to me it might be a replacement NTP daemon. | ||
...redacted... | |||
Further, running chronyc as root should not require me to use a "commandkey-password", especially since it seems to not work anyway. | |||
example below (HEX used was from /etc/chrony.keys - value here not shown, replaced with 1s) | |||
<pre> | |||
chronyc> password HEX:11111111111111111111111111111111111 | |||
501 Not authorised --- Reply not authenticated | |||
chronyc> | |||
</pre> | |||
Basically, the documentation, and usage of chronyd/chronyc is far too complicated, and appears to be geared toward a level of sophistication that is mind boggling. It is inconceivable that more than a handful of users will ever need to know such details, yet basic usage is buried in the documentation. All I as a basic user should need to know is how to get chrony to perform the equivalent of ntpdate to set the current time based upon some specified time server (probably running ntpd as a server :-} ), and then periodically poll a time server to keep the time in sync. | |||
Latest revision as of 09:30, 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 occurred to me it might be a replacement NTP daemon. ...redacted...
Further, running chronyc as root should not require me to use a "commandkey-password", especially since it seems to not work anyway. example below (HEX used was from /etc/chrony.keys - value here not shown, replaced with 1s)
chronyc> password HEX:11111111111111111111111111111111111 501 Not authorised --- Reply not authenticated chronyc>
Basically, the documentation, and usage of chronyd/chronyc is far too complicated, and appears to be geared toward a level of sophistication that is mind boggling. It is inconceivable that more than a handful of users will ever need to know such details, yet basic usage is buried in the documentation. All I as a basic user should need to know is how to get chrony to perform the equivalent of ntpdate to set the current time based upon some specified time server (probably running ntpd as a server :-} ), and then periodically poll a time server to keep the time in sync.