Bug 915270

Summary: Starting watchdog under systemd reports "cannot set scheduler"
Product: [Fedora] Fedora Reporter: Quentin Armitage <quentin>
Component: watchdogAssignee: Ales Ledvinka <aledvink>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: aledvink, rjones, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-07 12:04:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to watchdog.service - resolve issue none

Description Quentin Armitage 2013-02-25 11:02:54 UTC
Created attachment 702288 [details]
Patch to watchdog.service - resolve issue

Description of problem:
When starting watchdog with systemctl, it reports:
Feb 25 08:42:41 asenath watchdog[26006]: cannot set scheduler (errno = 1 = 'Operation not permitted')

When watchdog is run directly from command line it doesn't report the error.

Version-Release number of selected component (if applicable):
watchdog-5.12-2.fc18

How reproducible:
Always

Steps to Reproduce:
1.systemctl start watchdog
2.look at watchdog entries in /var/log/messages
3.
  
Actual results:
Error message above reported

Expected results:
No error

Additional info:
The attached patch for watchdog.service adds ControlGroup=cpu:/ which resolves the problem.

Comment 1 Ales Ledvinka 2013-11-07 12:04:31 UTC

*** This bug has been marked as a duplicate of bug 805397 ***