From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: breakage due to udev and hotplug both running hotplug scripts
Date: Tue, 06 Sep 2005 18:24:08 +0000 [thread overview]
Message-ID: <20050906182408.GA12865@wonderland.linux.it> (raw)
In-Reply-To: <200509062017.27346.baldrick@free.fr>
On Sep 06, Duncan Sands <baldrick@free.fr> wrote:
> I'm seeing the following: kobject_hotplug results in both
> udev and /sbin/hotplug running hotplug scripts. udevd gets
> the hotplug event via netlink thanks to kobject_hotplug
> calling send_uevent; /sbin/hotplug gets the hotplug event
> thanks to kobject_hotplug calling call_usermodehelper.
> Both calls eventually result in an agent being run. Am
> I right in thinking that my system is wrongly configured,
> and /sbin/hotplug should be disabled?
No, but there is still something wrong because udevd should ignore the
second event. I think this should fix it:
echo /sbin/udevsend > /proc/sys/kernel/hotplug
(or at least, I cannot reproduce this with debian/unstable.)
--
ciao,
Marco
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-09-06 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 18:17 breakage due to udev and hotplug both running hotplug scripts Duncan Sands
2005-09-06 18:24 ` Marco d'Itri [this message]
2005-09-06 18:35 ` Duncan Sands
2005-09-06 18:40 ` Marco d'Itri
2005-09-06 18:47 ` Duncan Sands
2005-09-07 12:39 ` Scott James Remnant
2005-09-07 12:50 ` Duncan Sands
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=20050906182408.GA12865@wonderland.linux.it \
--to=md@linux.it \
--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.