[Pkg-gtkpod-devel] Bug#742516: Please use udev monitor to discover new devices
Michael Biebl
biebl at debian.org
Mon Mar 24 17:00:13 UTC 2014
Package: usbmuxd
Version: 1.0.8-3
Severity: wishlist
Hi,
today's upload of usbmuxd prompted me to look
/lib/udev/rules.d/85-usbmuxd.rules which runs
RUN+="/usr/bin/pkill -x -SIGUSR2 usbmux" whenever a new device is
attached. The usbmuxd triggers a new device discovery whenever it
receives that signal.
Imho it would be much nicer to drop that kill invocation from the udev
rule and make the daemon listen on hardware changes via libudev using a
udev_monitor [0]
[0] https://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/libudev-udev-monitor.html
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages usbmuxd depends on:
ii adduser 3.113+nmu3
ii libc6 2.18-4
ii libplist1 1.10-1
ii libusb-1.0-0 2:1.0.17-1+b1
ii libusbmuxd2 1.0.8-3
usbmuxd recommends no packages.
usbmuxd suggests no packages.
-- no debconf information
More information about the Pkg-gtkpod-devel
mailing list