From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and systemd socket activation
Date: Thu, 14 Apr 2011 23:51:39 +0000 [thread overview]
Message-ID: <20110414235139.GA7171@kroah.com> (raw)
In-Reply-To: <BANLkTik0WUkH5Fu7LmVmptT9j4cDnBitAw@mail.gmail.com>
On Fri, Apr 15, 2011 at 01:34:50AM +0200, Kay Sievers wrote:
> Just a heads up,
> udev -git has new systemd socket/service files that will work only
> with current systemd -git. Older systemd versions with this version of
> udev will not properly boot up!
>
> The new udev.socket file will instruct systemd to bind the udev
> control socket and the netlink uevent socket, and let systemd
> auto-start udevd when any events arrive.
>
> It looks like this:
> # udevd runs
> $ pidof udevd
> 4544 4543 4401
>
> # kill it
> $ udevadm control --exit
> $ pidof udevd
>
> # trigger any device event
> $ echo change > /sys/class/mem/null/uevent
>
> # udevd is back and has handled this event
> $ pidof udevd
> 4624 4623
Very cool stuff, thanks for doing this work!
greg k-h
prev parent reply other threads:[~2011-04-14 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 23:34 udev and systemd socket activation Kay Sievers
2011-04-14 23:51 ` Greg KH [this message]
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=20110414235139.GA7171@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).