No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
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... | ...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) | |||
<nowiki> | |||
chronyc> password HEX:11111111111111111111111111111111111 | |||
501 Not authorised --- Reply not authenticated | |||
chronyc> | |||
</nowiki> | |||
Revision as of 09:11, 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...
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>