|
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | SEE ALSO | NOTES | COLOPHON |
SYSTEMD-SUSPEND.SERVICE(8) systemd-suspend.serviceSYSTEMD-SUSPEND.SERVICE(8)
systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-
sleep.service, systemd-suspend-then-hibernate.service, systemd-sleep
- System sleep state logic
systemd-suspend.service
systemd-hibernate.service
systemd-hybrid-sleep.service
systemd-suspend-then-hibernate.service
/usr/lib/systemd/system-sleep
systemd-suspend.service is a system service that is pulled in by
suspend.target and is responsible for the actual system suspend.
Similarly, systemd-hibernate.service is pulled in by hibernate.target
to execute the actual hibernation. Finally,
systemd-hybrid-sleep.service is pulled in by hybrid-sleep.target to
execute hybrid hibernation with system suspend and pulled in by
suspend-then-hibernate.target to execute system suspend with a
timeout that will activate hibernate later.
Immediately before entering system suspend and/or hibernation
systemd-suspend.service (and the other mentioned units, respectively)
will run all executables in /usr/lib/systemd/system-sleep/ and pass
two arguments to them. The first argument will be "pre", the second
either "suspend", "hibernate", "hybrid-sleep", or
"suspend-then-hibernate" depending on the chosen action. Immediately
after leaving system suspend and/or hibernation the same executables
are run, but the first argument is now "post". All executables in
this directory are executed in parallel, and execution of the action
is not continued until all executables have finished.
Note that scripts or binaries dropped in
/usr/lib/systemd/system-sleep/ are intended for local use only and
should be considered hacks. If applications want to react to system
suspend/hibernation and resume, they should rather use the Inhibitor
interface[1].
Note that systemd-suspend.service, systemd-hibernate.service,
systemd-hybrid-sleep.service, and
systemd-suspend-then-hibernate.service should never be executed
directly. Instead, trigger system sleep with a command such as
systemctl suspend or systemctl hibernate.
Internally, this service will echo a string like "mem" into
/sys/power/state, to trigger the actual system suspend. What exactly
is written where can be configured in the [Sleep] section of
/etc/systemd/sleep.conf or a sleep.conf.d file. See
systemd-sleep.conf(5).
systemd-sleep understands the following commands:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
suspend, hibernate, hybrid-sleep, suspend-then-hibernate
Suspend, hibernate, suspend then hibernate, or put the system to
hybrid sleep.
systemd-sleep.conf(5), systemd(1), systemctl(1), systemd.special(7),
systemd-halt.service(8)
1. Inhibitor interface
https://www.freedesktop.org/wiki/Software/systemd/inhibit
This page is part of the systemd (systemd system and service manager)
project. Information about the project can be found at
⟨http://www.freedesktop.org/wiki/Software/systemd⟩. If you have a bug
report for this manual page, see
⟨http://www.freedesktop.org/wiki/Software/systemd/#bugreports⟩. This
page was obtained from the project's upstream Git repository
⟨https://github.com/systemd/systemd.git⟩ on 2020-08-13. (At that
time, the date of the most recent commit that was found in the repos‐
itory was 2020-08-11.) If you discover any rendering problems in
this HTML version of the page, or you believe there is a better or
more up-to-date source for the page, or you have corrections or
improvements to the information in this COLOPHON (which is not part
of the original manual page), send a mail to man-pages@man7.org
systemd 246 SYSTEMD-SUSPEND.SERVICE(8)
Pages that refer to this page: sleep.conf.d(5) , systemd-sleep.conf(5) , 30-systemd-environment-d-generator(7) , systemd.index(7)