Bug 915270 - Starting watchdog under systemd reports "cannot set scheduler"
Summary: Starting watchdog under systemd reports "cannot set scheduler"
Keywords:
Status: CLOSED DUPLICATE of bug 805397
Alias: None
Product: Fedora
Classification: Fedora
Component: watchdog
Version: 18
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ales Ledvinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-25 11:02 UTC by Quentin Armitage
Modified: 2016-09-20 04:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-07 12:04:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch to watchdog.service - resolve issue (224 bytes, patch)
2013-02-25 11:02 UTC, Quentin Armitage
no flags Details | Diff

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 ***


Note You need to log in before you can comment on or make changes to this bug.