> "H. Peter Anvin" wrote:
> > David Harris wrote:
> > > > Depending on the kind of daemon used, it would either be respawned or
> > > > the info would get queued up until it is restarted. I don't think it's
> > > > particularly anything to worry about, though...
>
> > > If you re-spawn the daemon and it gets to see all of the events that have been
> > > stored up, it still does not have a proper view of the device configuration.
> > > The kernel really has to be smarter than just issuing events and buffering
> > > them.
>
> > It doesn't have to -- the additional information it needs is in the file
> > system.
>
> It doesn't have to, yes, but scanning the fs would be ugly and probably
> time consuming.
>
> IMHO /proc/device_events should be an ASCII list of device events, like
> described previously in this thread. Each line in that list, though,
> would need a timestamp of some sort.
Hrm. Sounds like a syslog-type thing. Could this be done by passing
data through syslog facilities?
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/