Re: [ACPI-sppt] Problems with Event-catching in acpid

From: "Sebastian Henschel" <[email protected]>

> Received at 2003-06-11 / 09:04 by Swen:
>>
>> I had a problem with the acpid-tool. It doesn't work, so i want! in
>> /var/log/acpid the events where shown correctly. I had create a file
>> /etc/acpi/events/power wich contents
>>
>> event=button/power.*
>> action=/etc/acpi/scripte/power.sh
>
> i remember there was an alternative in the regexp like
> event=button[/ ]power.*
> in my power-event, but this could be wrong.
>
> anyway, i now use only the default event which catches all:
>
> event=.*
> action=/etc/acpi/default.sh %e
>
> the event parsing is done in that script, check the attached default.sh

In your case, Swen, you'd need to catch the "LID" and "battery" events (the
latter quite possibly aren't generated!  I've never seen one, others have a
similar problem).  Using the default script Sebastian included, open and close
the lid a few times, and remove and insert the battery while on AC and let the
battery run down (if you don't have some BIOS powered alert like I do, be sure
to dismount all your partitions except the one with your syslog before it dies!
A journalling file system should be running on - at least - the logging
partition).

Then check the logs for the ACPI events to determine exactly which alerts are
being sent to acpid, and then write appropriate scripts.





-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.