From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Socket udev events (noobie)
Date: Sun, 09 Apr 2006 14:37:48 +0000 [thread overview]
Message-ID: <20060409143748.GA6942@vrfy.org> (raw)
In-Reply-To: <3a0f1c620604090727u14cff44au47a61c7191a553da@mail.gmail.com>
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&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-04-09 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 14:27 Socket udev events (noobie) Sting Zax
2006-04-09 14:37 ` Kay Sievers [this message]
2006-04-09 15:13 ` Moshe Yudkowsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060409143748.GA6942@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.