Re: alternate event logging proposal

[Tim Hockin]

> > a single device_event file that a daemon reads and dispatches events (I 
> > like this one because the daemon is already written, just poorly named - 
> > acpid)
> 
> Couldn't you just have the message sent to every process that has
> opened the file (and have every interested process open the file and
> read it in a non-blocking or blocking mode?)

Sure, but then every process that is concerned with a single event has to
not only receive every event, but parse every event.  And if this is to be
truly generic, that could be a lot of events.

> That seems to negate the need for something like acpid, but it does
> not preclude it's use.

True, and if a dev_event file were created, I'd consider doing it that way.
But in that case it's easier for apps to talk to eventd (nee acpid) and get
only the messages they want.

Tim