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

Mattia Dongili
2004-08-24T16:15:45Z

On Wed, Aug 25, 2004 at 12:23:04AM +0900, Hiroshi Miura wrote:
> 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
[...]
> I think it is enough.

but relying on the availability of acpid is not a good approach. And why
can acpid hijack /proc/acpi/event?
Allowing multiple readers is much better for every daemon that needs to
get acpi events.

just my 0.2 :)
--
mattia
:wq!