Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36339 - [ntp] Obsolete ControlGroup option in ntpd{,ate}.service file
Attached to Project:
Arch Linux
Opened by Leonid Isaev (lisaev) - Wednesday, 31 July 2013, 03:20 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 01 August 2013, 02:22 GMT
Opened by Leonid Isaev (lisaev) - Wednesday, 31 July 2013, 03:20 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 01 August 2013, 02:22 GMT
|
DetailsSince systemd 205, the ControlGroup option has been deprecated, but ntpd.service and ntpdate.service still contain "ControlGroup=cpu:/". As a result, each time those services are started, a warning is printed in the journal, e.g.
Jul 30 08:50:46 hermes systemd[1]: [/usr/lib/systemd/system/ntpd.service:9] Unknown lvalue 'ControlGroup' in section 'Service' I assume this option was put in order to make ntpd run with real-time scheduling. I wonder whether it is still required to specify explicitly with newer kernels/systemd, and whether a similar effect can be achieved with CPUSchedulingPolicy= and CPUSchedulingPolicy=. But in any case, the ControlGroup option needs to be removed... Thanks, Leonid. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Thursday, 01 August 2013, 02:22 GMT
Reason for closing: Fixed
Additional comments about closing: ntp-4.2.6.p5-16 in [testing]
Thursday, 01 August 2013, 02:22 GMT
Reason for closing: Fixed
Additional comments about closing: ntp-4.2.6.p5-16 in [testing]
Dave, you added the ControlGroup entry to ntpd.service and you obviously know more about systemd than me; what's your take on this?