Re: waiting for an unknown set of udev /dev entries to complete

[Kay Sievers <kay.sievers@vrfy.org>]

On Sun, Nov 20, 2005 at 09:23:33PM +0100, Marco d'Itri wrote:
> On Nov 20, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > You should be able to look for /dev/.udev/queue/*block*, and see if
> > there are events still running.
> I still see a problem with this design: there is a period (which may be
> easy to hit if the udevd is spawning the maximum allowed number of
> children), between when events are sent to udevd and when it starts
> processing them, when the on-disk queue is empty.

It's the received event queue, which is exported, not the processes
currently running. What problem do you see related to the maximum number
of childs?

There is still a small theorethical window between the module load
and the first event for a device created by that module, but it's unlikely
to hit that and it should be easy to work around that, if necessary.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel