From: Derek B. <dbr...@ne...> - 2003-03-27 13:25:25
|
From: "Stephen Torri" <st...@am...> > On Wed, 2003-03-26 at 07:57, Derek Broughton wrote: > > > ospmd aside - it really should be an improvement over acpid when done - acpid > > hasn't changed in months because there hasn't been any change to ACPI that would > > require a change to acpid. It simply listens for ACPI events and runs user > > defined scripts when they occur. If ACPI changes to trigger new events, acpid > > doesn't need to change, but the user would need to define new rules. > > The very fact of how to create rules and having no examples made me stop > trying to use acpid. If you have an example on a webpage that would be > great. If you're using debian, then there are examples in the package. Only two, but it's pretty trivial. If you're not using debian, then why not :-) The only 'secret' is the fact that the events shown - 'power' and 'ac' almost certainly don't exist. Well, anything that's unknown gets logged to syslog. Look for the ACPI events, use the names shown to create your own rules and scripts - we can't tell you what the events will be because they're defined at the DSDT level. derek |