| Server IP : 49.231.201.246 / Your IP : 216.73.216.149 Web Server : Apache/2.4.18 (Ubuntu) System : Linux 246 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64 User : root ( 0) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : exec,passthru,shell_exec,system,proc_open,popen,pcntl_exec MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/acpid/ |
Upload File : |
acpid for Debian
================
The acpid daemon can handle user defined events. Place event files under
/etc/acpi/events.
If an event occurs, acpid recurses through the event files in order to
see if the regex defined after "event" matches. If they do, action is
executed.
An example with /etc/acpi/events/powerbtn to handle presses on the power
button.
new style:
event=button/power .*
action=/etc/acpi/powerbtn.sh
old style:
event=button power.*
action=/etc/acpi/powerbtn.sh
to handle both styles:
event=button[ /]power
action=/etc/acpi/powerbtn.sh
Your script will get the complete event string (as reported by
/proc/acpid/events), if you use %e as a parameter of your script.
You may want to split this by calling set $*. $1 then holds the
event group, $2 takes the event and $3 and $4 take the values as
reported by the kernel.
When using acpid with modules, you can use /etc/default/acpid in order
to specify Linux kernel modules to be loaded at startup.