Description of problem: All 4&5 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. 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: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=88294 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.