Bug 19748

Summary: apmd service stop priority should be much lower
Product: [Retired] Red Hat Linux Reporter: Joe Krahn <krahn>
Component: apmdAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: low    
Version: 7.0Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-25 13:23:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Krahn 2000-10-25 13:23:29 UTC
The apmd service should be stopped early in a shutdown or reboot so that
the shutdown/reboot processwill not get suspended. This is relevant to all
systems, but especially for laptops. For example, I should be able to
initiate a shutdown, then close the laptop without waiting for it to
complete.
A stop level of 00 or 01 works for me.

Comment 1 Bernhard Rosenkraenzer 2000-11-02 12:19:20 UTC
I disagree. Turning off the machine before the shutdown process is finished (and therefore, all filesystems are unmounted) can be very harmful, therefore, if, for example, battery power runs low during shutdown, suspend-to-disk is preferrable over just cutting power.