From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: many instances of "/sbin/ifup ethx" coming from udev/hotplug
Date: Wed, 12 Dec 2007 05:42:04 +0000 [thread overview]
Message-ID: <1197438124.2579.62.camel@lov.site> (raw)
In-Reply-To: <475F04FC.2040802@nortel.com>
On Tue, 2007-12-11 at 16:10 -0600, Chris Friesen wrote:
> Kay Sievers wrote:
> > On Dec 11, 2007 10:45 PM, Chris Friesen <cfriesen@nortel.com> wrote:
>
> >>Can someone shed some light as to why ifup gets called from three
> >>different places for the same event, and whether it's expected to cause
> >>latency issues? Also, is there anything we can do to streamline this?
>
> > What distro is that? It sounds like a pretty broken setup. :)
>
> I don't think I should say, they might not appreciate it. ;)
:)
> So this is unusual?
It is.
> What's the expected path for ifup to be called in a
> current distro?
Usually it's called from a udev RUN rule only, and only
once. /sbin/hotplug does not even exist on most distros today.
Maybe you have the "hotplug" package installed and you shouldn't?
Kay
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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
prev parent reply other threads:[~2007-12-12 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 21:45 many instances of "/sbin/ifup ethx" coming from udev/hotplug Chris Friesen
2007-12-11 21:53 ` Kay Sievers
2007-12-11 22:10 ` Chris Friesen
2007-12-12 5:42 ` Kay Sievers [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=1197438124.2579.62.camel@lov.site \
--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).