On Sun, 2 Apr 2006, DJ Lucas wrote:
>
> Changed assignment for $failed to '2'. Test checks for 2 and displays 1720
> message if true. Will be committed and new tarball placed in my homedir
> momentarily.
>
Thanks. Assuming I'm testing the right version, I'm having trouble
understanding why it takes so long - the first couple of boots *seemed*
a lot quicker, then it was back to "how slow can we go ?" mode. Added
instrumentation after the loop to see what values are in the variables:
# until we know how to do better, just wait for _all_ events
#to finish
loop=300
confirm=0
while true ; do
sleep 0.1
test -d /dev/.udev/queue && confirm=0 || \
confirm=$(( $confirm + 1 ))
loop=$(( $loop - 1 ))
test $loop -gt 0 || break
test $confirm -lt 60 || break
done
echo "udev - loop exited with value $loop and confirm $confirm"
On this particular box, with my current kernel, the values are 236 or
237 for loop, and 60 for confirm. Can't get it to show anything
different. Adding another echo at the start of the loop confirms it
goes around for 2 or 3 passes before the queue exists, seems to complete
it within one pass (display didn't stay on screen long enough to be
certain), and then waits for a further 60 passes before deciding
it must have processed everything.
So, what is the derivation of this magic number 60, which I assume
approximates to 6 seconds ?
Ken
--
das eine Mal als Trag??die, das andere Mal als Farce--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
