linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: hotplugd - event serializer and multiplexer
Date: Sun, 07 Mar 2004 21:37:57 +0000	[thread overview]
Message-ID: <20040307213757.GA24298@vrfy.org> (raw)

Hi,
I've took our sweet udevd and made a generic hotplug event serializer.
It can replace the current /sbin/hotplug multiplexer bash script.

hotplugsend is invoked by the kernel and sends the data the kernel
provides over a domain socket to the hotplugd daemon. The daemon will
be started if not already running.

The hotplugd daemon reorders the events it receives, handles timeouts if
sequences are missing and executes all programs in /etc/hotplug.d/<subsys>/
thereafter in /etc/hotplug.d/default/ in each case in lexical order.

The programs are executed in the background, but only _one_ program runs
at any time for a single DEVPATH. No longer need for the various 'sleep 2'
all over the scripts. It's possible now to order the programs, so that
udev has already created all nodes, before the scripts are called.
udevd is no longer neccessary, we can call udev directly.

The maximum count of forked processes may be limited and is currently set
to 300.

It doesn't depend on any shell and therefore should be very fast for
a lot of devices connected at once. Hmm, I have only 4 :)

I know that most of us don't like a daemon for general hotplug, but I
wanted to try it. I expect more and more problems with the
syncronization of the hotplug scripts, so this is a possible solution.
No later event will ever beat the earlier for one device.

I've put this together today in 5 hours, so expect a very experimental
piece of code :)

Anybody interested, may look at it here:

  http://vrfy.org/projects/hotplugd/

thanks,
Kay


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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

             reply	other threads:[~2004-03-07 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 21:37 Kay Sievers [this message]
2004-03-08 17:06 ` hotplugd - event serializer and multiplexer Patrick Mansfield
2004-03-08 17:25 ` Kay Sievers
2004-03-08 20:51 ` Olaf Hering

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=20040307213757.GA24298@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 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).