|author||Victor Lowther <firstname.lastname@example.org>||2008-01-28 20:02:53 +0000|
|committer||Richard Hughes <email@example.com>||2008-01-28 20:02:53 +0000|
Minor updates to README -- /etc/pm/hooks has not existed in a long time.
Diffstat (limited to 'README')
1 files changed, 4 insertions, 4 deletions
@@ -26,7 +26,7 @@ file into the hooks directory, for example:
How do "hooks" work?
-* You put a file in /etc/pm/hooks, which is executable. When suspend or
+* You put an executable file in /etc/pm/sleep.d. When suspend or
hibernate is called, several things happen:
1) a new virtual terminal is alloced and switched to
@@ -34,9 +34,9 @@ How do "hooks" work?
modified by end-users.
3) /etc/pm/config.d/* are evaluated in C sort order. These files can be
provided by individual packages outside of pm-utils. If a global config
- variable is set, the value set to will be appended to the previous value.
+ variable is set, the value set to will overwrite the previous value.
If any other variable is set, it will be ignored.
- 4) each of /etc/pm/hooks/* are executed in C sort order. The first command
+ 4) each of /etc/pm/sleep.d/* are executed in C sort order. The first command
line argument is "suspend" or "hibernate". These files may source
configuration files from /etc/pm/config.d/ on their own in order to pick
up variables set there that aren't part of the global list. Note that
@@ -45,7 +45,7 @@ How do "hooks" work?
will clobber any such variables.
5) the system suspends or hibernates.
6) some event happens to wake the machine up
- 7) each of /etc/pm/hooks/* are executed in reverse C sort order. The first
+ 7) each of /etc/pm/sleep.d/* are executed in reverse C sort order. The first
command line argument is "resume" or "thaw".
8) the system switches back to the original virtual terminal from step 1.