Re: [PATCH 1/4] properly create kobjects in acpi/scan.c

Hiroshi Miura
2004-08-24T15:23:04Z

Hi,

At Tue, 24 Aug 2004 01:34:15 -0500,
Dmitry Torokhov wrote:
> 04-acpi-multiple-readers.patch
> - allow multiple readrs access /proc/acpi/event, every event is
> delivered to all readers. Also limit number of pending events
> to 64 (per reader) so if reader is stuck ACPI does not consume
> all memory.
>
> Can be user by various daemons, I could see cpufreqd listening
> for battery insertion/removal events and debugging is much
> easier too.

'acpid' has soket interface for other daemon/utillities.

from man acpid
In addition to rule files, acpid also accepts connections on a UNIX
domain socket (/var/run/acpid.socket by default). Any application may
connect to this socket. Once connected, acpid will send the text of
all ACPI events to the client. The client has the responsibility of
filtering for messages about which it cares. acpid will not close the
client socket except in the case of a SIGHUP or acpid exiting.

I think it is enough.

If allow multiple readers, acpid and other tool need some lock facility to avoid
unwanted multiple event handling.

--
Hiroshi Miura --- http://www.da-cha.org/ --- miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org
NTTDATA Corp. OpenSource Software Center. --- miurahr-3MafRgGXt7BL9jVzuh4AOg@public.gmane.org
NTTDATA Intellilink Corp. OpenSource Engineering Dev. -- miurahr-w0OK63jvRlAuJ+9fw/WgBHgSJqDPrsil@public.gmane.org
Key fingerprint = 9117 9407 5684 FBF1 4063 15B4 401D D077 04AB 8617