public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
To: ACPI Development - Sourceforge
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Daemon that handles ACPI
Date: Thu, 27 Mar 2003 09:25:13 -0400	[thread overview]
Message-ID: <024101c2f464$4c3a20a0$3746028e@bio.dfo.ca> (raw)
In-Reply-To: 1048723591.3593.2.camel@base.torri.linux

From: "Stephen Torri" <storri-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>

> 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



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

  parent reply	other threads:[~2003-03-27 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  2:07 Daemon that handles ACPI Stephen Torri
     [not found] ` <1048644460.2910.39.camel-NN61vRp3iFIP0m8IYG7BWw@public.gmane.org>
2003-03-26  2:33   ` Randy.Dunlap
2003-03-26 13:57     ` Derek Broughton
     [not found]       ` <005901c2f39f$ac481530$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-03-27  0:06         ` Stephen Torri
     [not found]           ` <1048723591.3593.2.camel-NN61vRp3iFIP0m8IYG7BWw@public.gmane.org>
2003-03-27  1:46             ` Sérgio Monteiro Basto
     [not found]               ` <1048729567.1490.17.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-03-27 15:08                 ` Ducrot Bruno
2003-03-27 13:25           ` Derek Broughton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27  2:24 Grover, Andrew

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='024101c2f464$4c3a20a0$3746028e@bio.dfo.ca' \
    --to=dbroughton-f3m4/jxepmf3fq9qlvqp4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox