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#34051 - [watchdog] Starting watchdog via systemd results in a cannot set scheduler error.
Attached to Project:
Arch Linux
Opened by Jameson Pugh (ImNtReal) - Wednesday, 27 February 2013, 17:40 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 02:31 GMT
Opened by Jameson Pugh (ImNtReal) - Wednesday, 27 February 2013, 17:40 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 02:31 GMT
|
DetailsDescription:
Starting watchdog via systemd results in a cannot set scheduler error. According to https://bugzilla.redhat.com/show_bug.cgi?id=915270, simply adding ControlGroup=cpu:/ to the unit file will correct the problem. Additional info: * watchdog 5.13-1 * watchdog[29871]: cannot set scheduler (errno = 1 = 'Operation not permitted') Steps to reproduce: 1. # pacman -S watchdog 2. # systemctl start watchdog.service 3. # systemctl status watchdog.service |
This task depends upon
The problem remains that systemd cannot set the scheduler...
is this issue still valid?