> 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?)
That seems to negate the need for something like acpid, but it does
not preclude it's use.
>
> For things like netif_carrier, poll() is probably best - the DHCP client
> can be fully self contained, and not need an eventd to alert it to a
> signal change. Of course, acpid does support UNIX socket connections
> from apps like DHCP....
I would prefer an event, and it can still be self contained if my
idea above is actually workable.
Ben
>
>
>
-- Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/