acpid - Advanced Configuration and Power Interface event daemon
acpid is designed to notify user-space programs of ACPI events. acpid should be started during the system boot, and will run as a background process, by default. It will open an events file (/proc/acpi/event by default) and attempt to read whole lines. When a line is received (an event), acpid will examine a list of rules, and execute the rules that match the event.
Rules are defined by simple configuration files. acpid will look in a configuration directory (/etc/acpi/events by default), and parse all files that fit to a runparts style naming convention. This means that files containing a dot and contain characters different from a-z and 0-9 would be ignored. Debian implementation differs at this point from standard acpid. Each file must define two things: an event and an action. Any blank lines, or lines where the first character is a pound sign (’#’) are ignored. Extraneous lines are flagged as warnings, but are not fatal. Each line has three tokens: the key, a literal equal sign, and the value. The key can be up to 63 characters, and is caseinsensitive (but whitespace matters). The value can be up to 511 characters, and is case and whitespace sensitive.
The event value is a regular expression (see regcomp(3) ), against which events are matched.
The action value is a commandline, which will be invoked via /bin/sh whenever an event matching the rule in question occurs. The commandline may include shell-special characters, and they will be preserved. The only special characters in an action value are “%” escaped. The string “%e” will be replaced by the literal text of the event for which the action was invoked. This string may contain spaces, so the commandline must take care to quote the “%e” if it wants a single token. The string “%%” will be replaced by a literal “%". All other “%” escapes are reserved, and will cause a rule to not load.
This feature allows multiple rules to be defined for the same event (though no ordering is guaranteed), as well as one rule to be defined for multiple events. To force acpid to reload the rule configuration, send it a SIGHUP.
In addition to rule files, acpid also accepts connections on a UNIX domain socket (/var/run/acpid.socket by default). Any application may connect to this socket. Once connected, acpid will send the text of all ACPI events to the client. The client has the responsibility of filtering for messages about which it cares. acpid will not close the client socket except in the case of a SIGHUP or acpid exiting.
acpid will log all of its activities, as well as the stdout and stderr of any actions to syslog.
All the default file and directories can be changed with commandline options.
-c, --confdir directory
This option changes the directory in which acpid looks for rule configuration files. Default is /etc/acpi/events.
This example - placed in /etc/acpi/events/power - will shut down your system if you press the power button.
The script power.sh gets called and will see the complete event string as parameter $1.
acpid should work on any linux kernel released since 2003.
There are no known bugs. To file bug reports, see AUTHORS below.
Tim Hockin <firstname.lastname@example.org>