From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 09 Apr 2006 14:37:48 +0000 Subject: Re: Socket udev events (noobie) Message-Id: <20060409143748.GA6942@vrfy.org> List-Id: References: <3a0f1c620604090727u14cff44au47a61c7191a553da@mail.gmail.com> In-Reply-To: <3a0f1c620604090727u14cff44au47a61c7191a553da@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sun, Apr 09, 2006 at 05:27:21PM +0300, Sting Zax wrote: > Hello, > I saw that in udev.c , when getting socket events > (name_loop->name is "socket:"), than > we call pass_env_to_socket and not runn the program is > in all other cases , where the program name is in > fact name_loop->name (by calling run_program). > My question is : which are the eventes which their name > is "socket:"? These are not special events, these are RUN keys with the prefix "socket:" plus the name of an abstract namespace socket where the event is passed to instead of forking a program. Udevmonitor is connected like this: RUN+="socket:/org/kernel/udev/monitor" It listens on the socket with the specified name. Kay ------------------------------------------------------- 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