linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] let /sbin/hotplug execute udev earlier
Date: Sun, 05 Sep 2004 08:07:52 +0000	[thread overview]
Message-ID: <20040905080752.GB11337@kroah.com> (raw)

On Sun, Aug 29, 2004 at 10:51:56PM +0200, Kay Sievers wrote:
> We ran into problems with all the /etc/hotplug.d/ scripts that sleep for
> the sysfs files or for other reasons. Anyway, it takes much too much time
> before udev is executed.
> HAL has its own notifier in /etc/hotplug.d/ and also waits for the
> dev.d/events with the same SEQNUM. Sometimes it take 25 seconds between
> these two events, cause the other scripts are sleeping too much :)
> 
> Attached is a patch that installs the udevsend symlink as
> 10-udev.hotplug instead of udev.hotplug, to be executed earlier.
> 
> [kay@pim udev.kay]$ tree /etc/hotplug.d/
> /etc/hotplug.d/
> `-- default
>     |-- 10-udev.hotplug -> /sbin/udevsend
>     |-- 20-hal.hotplug -> /usr/libexec/hal.hotplug
>     `-- default.hotplug

That makes sense.  Applied, thanks.

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&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-09-05  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05  8:07 Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-29 20:51 [patch] let /sbin/hotplug execute udev earlier Kay Sievers

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=20040905080752.GB11337@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).