%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
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.