On Thursday 19 January 2006 15:46, Joaquim Ortega wrote: > On 18 January 2006, Christofer Martin wrote: > > udev shouldn't be running scripts in /etc/hotplug at all. These are > > legacy hotplug scripts, for non-udev users. If udev is still running > > those scripts, then file a bug against udev. I doubt very much that it > > is, however. I suggest looking again, or giving me more detail > > concerning how you arrived at your findings. > > It seems to me that the hotplug script is invoked by udev instructed from > the rules in /etc/udev/logitechmouse.rules that states for instance > SYSFS{idProduct}=="c00e", SYSFS{idVendor}=="046d", > RUN+="/etc/hotplug/usb/logitechmouse"
In KDE 3.5, it no longer does this. But yes, now I recall that it does do what you say with KDE 3.4; however, this practice matches the scripts of many other packages (libgphoto2, etc.) and still should not result in net boot delays. Sam Morris wrote: > The script /etc/hotplug/usb/logitechmouse causes a long delay during > boot, while udev waits 'for /dev to by fully populated'. From my tests, > it seems that DEVICE isn't even set in the script's environment, so the > script is timing out while waiting for a file with an empty file to be > created. I suggest adding something like this to the top of the script: DEVICE, etc. should be passed from udev to the script. That's how the script works (again, it's the same with libgphoto2). Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]