From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harald Hoyer Date: Fri, 07 Aug 2009 12:26:19 +0000 Subject: Re: udev 145, when are events fully processed? Message-Id: <4A7C1D6B.8040308@redhat.com> List-Id: References: <4A749D9E.3020709@lbsd.net> In-Reply-To: <4A749D9E.3020709@lbsd.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On 08/01/2009 09:55 PM, Nigel Kukard wrote: > Hi Guys, > > Trying to figure something out here, using the following I'm seeing a > delay in the creation of block devices in /dev ... > > # trigger the sorted events > echo -e '\000\000\000\000'> /proc/sys/kernel/hotplug > > rm -fr /dev/.udev> /dev/null 2>&1 > mkdir -p /dev/.udev> /dev/null 2>&1 > /sbin/udevd > > # Not entirely sure what this is for > /sbin/udevadm control --env=STARTUP=1 > /sbin/udevadm trigger > /sbin/udevadm settle settle should have waited until all events have been processed > # Nor sure what this does > /sbin/udevadm control --env=STARTUP> > > I think my problem is, while all the events have been sent to udevd > there is a delay if I do a "fsck LABEL=root" straight on say the next > line, a "ls" shows that none of the block devices exist until a second > or two later. A sleep 5 before my "ls" works around this and the block > devices show up. > > Any ideas how I can determine once all udev events have finished > processing so I can continue boot? check would look like: /sbin/udevadm settle --timeout=0 || echo "Still not all udev events processed" waiting should be: /sbin/udevadm settle > > > Kind Regards > Nigel > -- > To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html