Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1162045

Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep State
Product: [Retired] Fedora Documentation Reporter: bob <redzilla.coralnut>
Component: power-management-guideAssignee: Petr Bokoc <pbokoc>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: develCC: zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 15:30:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bob 2014-11-10 06:27:21 UTC
Description of problem:

F20 Power Management Guide does not address the hooks into the sleep system provided by systemd.  Ever since p,m-utils was deprecated there have been no Fedora/RHAT resources available that discuss how to utilize the hooks into the sleep system to prevent entry into the sleep state.

Example: in the era of pm-utils (going back to what, F15?) one could write scripts to suppress the transition to S3 if a desirable network connection were established that should not be interrupted.  All that was required was to place the script in /etc/pm/sleep.d/ and have it issue a non-zero exit code if sleep should be suppressed.  When the goto sleep process prepared for sleep by executing the script, the script could deliver a non-zero exit code and prevent entry into the sleep state.

Now that pm-utils has been deprecated and replaced with systemd, Fedora now ignores any/all scripts in /etc/pm/*.  That isn't a problem.  What *IS* a problem, though, is that for the past 5 releases of Fedora, the Power Management Guide has completely ignored the topic of how to use custom scripts to prevent entry into the sleep state.  As a result, our only options are to look for help and examples in other distributions.


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

F20, F21

How reproducible:

N/A.  The documentation doesn't address the problem.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Petr Bokoc 2019-11-07 15:30:10 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.