From: Kay Sievers Date: Fri, 02 Dec 2005 03:03:15 +0000 Subject: Re: problem with PROGRAM Message-Id: <20051202030315.GB19593@vrfy.org> List-Id: References: <438D4B0F.5050303@magellan-technology.com> In-Reply-To: <438D4B0F.5050303@magellan-technology.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Dec 01, 2005 at 04:00:49PM +1100, Aras Vaichas wrote: > Aras Vaichas wrote: > >rule: > >KERNEL="usb[0-9]", ACTION="add", ENV{PHYSDEVDRIVER}="usbnet", > >PROGRAM="/etc/udev/scripts/start_autoipd.sh %k" > > UPDATE: > > I changed the rule from PROGRAM to RUN like so: > KERNEL="usb[0-9]", ACTION="add", ENV{PHYSDEVDRIVER}="usbnet", > RUN+="/etc/udev/scripts/start_autoipd.sh %k" > > and the process no longer becomes a zombie and it all appears to work > correctly. > > Why would PROGRAM cause this situation but RUN doesn't? PROGRAM is to request information from external programs to name a device. It is not to start or run anything else. RUN will run after the device node is created. But there is no real reason to behave differently in your case. Again, make sure you are detaching immediately from the event process, and don't block longer than needed, not in PROGRAM, and not in RUN. It will cause problems for the event sequence handling. Start your program in the background and just exit. Kay ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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