FS#55324 - [chrony] service disabled after a recent rename from chrony to chronyd

Attached to Project: Community Packages
Opened by LightDot (lightdot) - Tuesday, 29 August 2017, 00:41 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 29 August 2017, 00:55 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The chrony service was recently (3.1-1 -> 3.1-2) renamed from chrony to chronyd. This in practice disables the chrony daemon on all systems that had it previously enabled, leaving systems without NTP. User has to re-enable chronyd manually.

After the update, the obsolete symlink to chrony.service remains:

ls -als /etc/systemd/system/multi-user.target.wants/chr*
0 lrwxrwxrwx 1 root root 38 May 2 13:16 /etc/systemd/system/multi-user.target.wants/chrony.service -> /usr/lib/systemd/system/chrony.service


The upgrade does state "crony.service was renamed to cronyd.service!" but to me it was not immediately obvious that any user action is required.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Tuesday, 29 August 2017, 00:55 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Given that you had to enable the service, you should also know how to re-enable it. Users are expected to know how systemd services work when working with systemd services, this isn't Debian.

Arch *will not* manage your services for you.

Loading...