Bug 105687 - sysctl not reloaded after an `apmd --suspend`
Summary: sysctl not reloaded after an `apmd --suspend`
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apmd
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-26 16:04 UTC by Avi Alkalay
Modified: 2014-03-17 02:38 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-02-02 22:56:42 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Avi Alkalay 2003-09-26 16:04:42 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux)

Description of problem:
sysctl parameters (like net.ipv4.ip_forward = 1) are not reloaded after an apm --suspend

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

How reproducible:
Always

Steps to Reproduce:
1. Set some parameters in /etc/sysctl.conf (like net.ipv4.ip_forward = 1)
2. Execute `apm --suspend` and wait for complete suspend
3. Unsuspend
4. Check sysctl environment with `/sbin/sysctl -a`
    

Actual Results:  /etc/sysctl.conf parameters are not reloaded

Expected Results:  /etc/sysctl.conf parameters to be reloaded

Additional info:

After an unsuspend I have to manually execute `sysctl -p`
Comment 1 Bill Nottingham 2005-02-02 22:56:42 UTC 
Closing out bugs on older unsupported releases. Apologies for any lack
of response. Please reopen if it persists on current releases such as
Fedora Core 3.

This should be handled by the network restarting.
Note You need to log in before you can comment on or make changes to this bug.