[Bug 1162045] New: Power Mgmt Guide needs to Address Howto Suppress Sleep State

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1162045

            Bug ID: 1162045
           Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep
                    State
           Product: Fedora Documentation
           Version: devel
         Component: power-management-guide
          Severity: low
          Assignee: yruseva at redhat.com
          Reporter: redzilla.coralnut at xoxy.net
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: ddomingo at redhat.com, yruseva at redhat.com,
                    zach at oglesby.co



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:

-- 
You are receiving this mail because:
You are the QA Contact for the bug.