Public bug reported:
Binary package hint: udev
My system randomly ends up in condition after bootup where I have 3
instances of udevd running of which upstart is only aware of one. None
of them seem properly working as ethernet device renaming has not been
finalized.
My guess for the reason might be that:
- udev.conf starts up udevd
- udevtrigger.conf starts up udevadm trigger based on condition 'start on
started udev'
Isn't this a obvious race? I don't think udevd is guaranteed even to hit
main() by the time udevadm trigger can be run (IMHO once its forked
upstart considers it running). My guess is that those 2 extra udevd
instances come from kernel trying to start up new instance of udevd as
one is not registered yet.
For now I'll just fix this with udevtrigger pre-start script that sleeps
for few seconds..
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
karmic: udevadm trigger run races udevd startup
https://bugs.launchpad.net/bugs/489101
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
