Bug 231655 - [RFE] ability run sysctl after modules are loaded
[RFE] ability run sysctl after modules are loaded
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: module-init-tools (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jon Masters
Depends On:
  Show dependency treegraph
Reported: 2007-03-09 15:27 EST by Neil Doane
Modified: 2007-11-16 20:14 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-22 15:59:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neil Doane 2007-03-09 15:27:34 EST
Description of problem:
All 4&5

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

How reproducible:

Steps to Reproduce:
Actual results:
Parameters in sysctl.conf relating to modules are not set after modules load.

Expected results:
Parameters in sysctl.conf are set after modules load.  

Additional info:

Please see: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189310 for
detailed additional info.
...see also:
For an example of this behavior.

I've previous submitted this as an initscript RFE, but it was closed as
unfixable and the recommendation was one of two alternatives, either the
creation of modprobe.conf entries that run sysctl on module load, or udev rules
that run sysctl after module registration.  Seems like the most easily
configurable choice would be some type of modprobe.conf entry that caused sysctl
to be run.

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