Looking through the udev code, I can't really see any reason that pkill would be more effective than udevadm control --exit (as earlier reported), except if udevd has somehow lost track of a worker, because both are supposed to send SIGTERM to all the processes. Furthermore, if udevadm is doing what it ought, I would expect the 'udevadm control --exit' command to block until either the udevd processes have all died, or the timeout is reached, thus blocking the boot. But I don't remember anyone saying the boot itself was slow when hitting this bug - so maybe one issue here is that udevadm is failing to wait for udevd to exit before continuing.
-- 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
