The scripts in acpi-support can potentially be triggered in more than one way. The classic example is to have /etc/acpi/events/sleepbtn call the sleep script. In an environment where you're running an application like gnome-power-manager, this isn't what you want to happen. Once the user can determine policy, the hardcoded events should do nothing. That's the reason for checking whether gnome-power-manager or similar are running, and refusing to run in that case. HAL should pass the force argument in order to cause the script to run anyway, since HAL will only be triggered by policy manager events in any case.
-- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
