http://bugs.linuxfromscratch.org/show_bug.cgi?id=874
------- Additional Comments From [EMAIL PROTECTED] 2005-11-07 06:41 ------- Here is what happens: 1) the hotplug initscript probes some modules 2) modules generate hotplug events 3) the first event starts udevsend (because it is in /proc/sys/kernel/hotplug) 4) udevsend it starts udevd 5) udevd successfully binds to the socket 5) same for the next event, but the second udevd doesn't successfully bind to the socket (because the first udevd is already bound to it), and logs this ugly message to the console. Setting /proc/sys/kernel/hotplug to empty value avoids the second udevsend (and thus the second udevd) at all. The hack is incomplete BTW. After setting /proc/sys/kernel/hotplug to empty value but before running udevstart, the script must do the following: UDEVD_EXPECTED_SEQNUM=$(($(cat /sys/kernel/hotplug_seqnum) + 1)) udevd --daemon Otherwise udevd is not started at all. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are the QA contact for the bug, or are watching the QA contact. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
