K2LL33D SHELL

 Apache/2.4.7 (Ubuntu)
 Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64
 uid=33(www-data) gid=33(www-data) groups=33(www-data)
 safemode : OFF
 MySQL: ON | Perl: ON | cURL: OFF | WGet: ON
  >  / usr / share / doc / acpid /
server ip : 104.21.89.46

your ip : 172.70.80.98

H O M E


Filename/usr/share/doc/acpid/README.Debian
Size997
Permissionrw-r--r--
Ownerroot : root
Create time27-Apr-2025 09:55
Last modified04-Apr-2014 02:41
Last accessed06-Jul-2025 18:48
Actionsedit | rename | delete | download (gzip)
Viewtext | code | image
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.