OXIESEC PANEL
- Current Dir:
/
/
usr
/
share
/
doc
/
acpid
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
11/10/2024 09:42:49 AM
rwxr-xr-x
📄
README
2.95 KB
08/16/2015 08:18:22 PM
rw-r--r--
📄
README.Debian
997 bytes
04/22/2017 01:14:06 PM
rw-r--r--
📄
changelog.Debian.gz
1.88 KB
04/28/2017 04:28:10 AM
rw-r--r--
📄
copyright
671 bytes
04/22/2017 01:14:06 PM
rw-r--r--
📁
examples
-
10/21/2019 03:49:19 PM
rwxr-xr-x
Editing: README.Debian
Close
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.