Bug 756937 - sysctl.d scripts are not executed
Summary: sysctl.d scripts are not executed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-25 08:21 UTC by Carlo de Wolf
Modified: 2014-03-17 03:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-20 18:53:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Carlo de Wolf 2011-11-25 08:21:57 UTC
Description of problem:

Settings specified in a sysctl.d file are not applied on boot.

Version-Release number of selected component (if applicable):

initscripts-9.30.1-1.fc15.x86_64
procps-3.2.8-22.20110302git.fc15.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. I've created a sysctl.d file according to the instructions at:
http://confluence.jetbrains.net/display/IDEADEV/Inotify+Watches+Limit

# cat /etc/sysctl.d/intellij
fs.inotify.max_user_watches = 524288

2. Reboot
  
Actual results:

When I reboot however the setting is not applied.
# sysctl fs.inotify.max_user_watches
fs.inotify.max_user_watches = 8192

Expected results:

# sysctl fs.inotify.max_user_watches
fs.inotify.max_user_watches = 524288

Additional info:

The only place where sysctl.d is applied is from /etc/init.d/network. So as I work-around I enabled the network service, leading to 708207 [1].

Based on 593211 [2] and 680529 [3] it seems to me that execution sysctl.d at the correct moment is a concern of the procps package, not initscripts.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=708207
[2] https://bugzilla.redhat.com/show_bug.cgi?id=593211
[3] https://bugzilla.redhat.com/show_bug.cgi?id=680529

Comment 1 Bill Nottingham 2011-11-28 21:27:44 UTC
sysctl.d files need to end in .conf. See 'man sysctl.d'.

(Arguably, the initscripts support should be changed to enforce this.)


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