Migration to managed hotplug events incomplete
|Reported by:||Owned by:|
Although the "udev" initscript now sets /proc/sys/kernel/hotplug to /sbin/udevsend, there are a few more steps to do. 1) To avoid future incarnations of Bug 842 and prevent junk device nodes from appearing in the real /dev (right now we just ignore them), add the following commands to hotplug installation instructions: rm /sbin/hotplug # because /sbin/udevsend does everything /sbin/hotplug did sed -i s@/sbin/hotplug@/etc/hotplug/pci.agent@ /etc/hotplug/pci.rc In "Short descriptions", remove the description of /sbin/hotplug, or, better, replace it with the reference to udevsend. 2) On the udev page, optionally add the following command: rm /etc/hotplug.d/default/10-udev.hotplug That symlink is needed only in non-managed mode. In managed mode, if this symlink is present, the following happens: a) The kernel calls /sbin/udevsend in order to inform userspace about the hotplug event b) udevsend transfers that information to udevd c) udevd calls handlers in /etc/dev.d and /etc/hotplug.d, including that symlink d) /sbin/udevsend is called again through that symlink. It detects a loop and exits immediately. Removal of that symlink optimizes things a bit by removing that loop.