FS#58411 - [chrony] Use upstream systemd unit files chrony{d,-wait}.service

Attached to Project: Community Packages
Opened by Indrajit Raychaudhuri (indrajitr) - Tuesday, 01 May 2018, 03:13 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 10 May 2018, 01:09 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
chronyd.service currently bundled with chrony is quite outdated and can be replaced with upstream chronyd.service [1].
Additionally chrony-wait.service [2] can possibly be added as well.

This would also help us resolve the following issues (without resorting to custom systemd unit file overrides):
* Explicitly mark conflict with ntpd.service (in addition to systemd-timesyncd.service) via Conflicts directive
* Add directives ConditionCapability, PrivateTmp, ProtectHome, and ProtectSystem

[1] https://git.tuxfamily.org/chrony/chrony.git/tree/examples/chronyd.service
[2] https://git.tuxfamily.org/chrony/chrony.git/tree/examples/chrony-wait.service

Additional info:
* package version(s): chrony 3.2
* config files: /usr/lib/systemd/system/chrony{d,-wait}.service
This task depends upon

Closed by  Levente Polyak (anthraxx)
Thursday, 10 May 2018, 01:09 GMT
Reason for closing:  Implemented
Additional comments about closing:  3.3-1

Loading...