From 0127336c01198ef210882207d24257cb3752718b Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 26 Jun 2012 17:50:29 +0200 Subject: man: document systemd-halt.service and friends --- man/systemd-suspend.service.xml | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-) (limited to 'man/systemd-suspend.service.xml') diff --git a/man/systemd-suspend.service.xml b/man/systemd-suspend.service.xml index dea778fbec..1ae742bcd8 100644 --- a/man/systemd-suspend.service.xml +++ b/man/systemd-suspend.service.xml @@ -46,7 +46,7 @@ systemd-suspend.service systemd-hibernate.service systemd-sleep - systemd System Suspend/Hibernate Logic + systemd System Sleep State Logic @@ -74,13 +74,14 @@ and pass two arguments to them. The first argument will be "pre", the second either "suspend" or - "hibernate", depending on the chosen - action. Immediately after leaving system suspend and - 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 - before all executables finished. + "hibernate", depending on the + chosen action. Immediately after leaving system + suspend and 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 before all executables + finished. Note that scripts or binaries dropped in /usr/lib/systemd/system-sleep/ @@ -89,13 +90,20 @@ of system suspend and resume there are much nicer interfaces available. + Note that + systemd-suspend.service and + systemd-hibernate.service should + never be executed directly. Instead, trigger system + sleep states with a command such as "systemctl + suspend" or suchlike. See Also systemd1, - systemd.special7 + systemctl1, + systemd.special7, systemd-halt.service8 -- cgit v1.2.1