From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Date: Tue, 18 Apr 2006 02:30:34 +0000 Subject: Re: Integrate udevsettle with udevtrigger? Message-Id: <44444F4A.1010108@ums.usu.ru> List-Id: References: <444421CE.3030206@kadzban.is-a-geek.net> In-Reply-To: <444421CE.3030206@kadzban.is-a-geek.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Bryan Kadzban wrote: > (I basically cut-and-pasted udevsettle's code into the function; it's > possible that something got screwed up there. The code compiles OK for > me, though, and it hasn't leaked any more uevents than "udevtrigger && > udevsettle" over ~6-8 bootups. To check for leaks, I'm doing what > Alexander did[1]: putting an ACTION="add" RUN+="bug" rule last, > clearing out the /dev/bug file after the udevtrigger --wait call, > sleeping 6 seconds, and looking for anything in /dev/bug. Both setups > leak events in the presence of usb-storage devices, but I think that's a > known issue. If I have only USB-HID devices plugged in, that works OK > whether I use "udevtrigger --wait" or "udevtrigger && udevsettle".) Does the leak go away if you use the "ub" driver instead of "usb-storage"? -- Alexander E. Patrakov ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel