daniel at freedesktop.org
Thu Mar 9 10:16:49 PST 2006
On Thu, Mar 09, 2006 at 07:15:38PM +0200, Kalle Vahlman wrote:
> I was under the impression that it was a hardware event that userspace
> programs were required to react to, not a userspace program requesting
> something from other userspace programs. So the interface would be
> org.foo.ACPI or maybe something more general.
It's a hardware event that the kernel catches. The kernel then signals
out through /proc/acpi/event (usually to acpid). So, in this case,
acpid tries to let programs know that it's going down. It's not like
the kernel sends SIGACPI to all processes or something.
Maybe we could have acpid providing org.foo.acpid, and gnome-screensaver
or whatever can listen for events on that? That way, your policy on
when to lock the screen or whatever could be per-session, rather than
global (lock your screens now! or else).
Note that the reason the Ubuntu ACPI scripts grep utmp or whatever and
work out the current user is so they can use xscreensaver's own IPC
interface; until recently, it called xscreensaver-command -lock.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20060309/a1bd7cf2/attachment.pgp
More information about the dbus