Description of problem: Version-Release number of selected component (if applicable): All 4 & 5. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: 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.
There is no resident portion of initscripts that would be able to catch these events in a way that you could hook in. Suggestions would be: - modprobe.conf entries that run sysctl on module load - udev rules that run sysctl on module registration