On Fri, Oct 07, 2011 at 09:55:52PM -0000, Eduard Hasenleithner wrote: > And I think, I have also found the reason. The scripts in the initial > ramdisk are executed with "set -e". In this case your pkill fails and > aborts the execution of init-bottom/udev. And in the "normal" case, > init-bottom/udev aborts because "udevadm control --exit" reports by > means of its return value that, after timeout (yes, udevadm has its own > timeout of 60s!), the exit failed.
Oh, right. pkill exits non-zero if it doesn't find anything, and udevadm exits non-zero if the timeout is hit. And the udevadm timeout is 60 seconds (not mentioned in the manpage), which just about ensures that the udevadm timeout will be hit before the udevd one. So yeah, that patch was certainly a dud. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
