many instances of "/sbin/ifup ethx" coming from udev/hotplug

many instances of "/sbin/ifup ethx" coming from udev/hotplug

[Chris Friesen]

Hi all,

We're running a 2.6.14 kernel and have a situation where multiple (20 or 
so) ethx devices are being created in about 3 seconds.  This appears to 
cause latency issues for other tasks on the system due to all the 
"/sbin/ifup ethx" processes that get created.

We're seeing these processes being created by udevd directly, by 
/sbin/hotplug, and by /etc/sysconfig/network-scripts/net.hotplug (which 
is in turn created by udevd).

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?

Thanks,

Chris

-------------------------------------------------------------------------
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

Re: many instances of "/sbin/ifup ethx" coming from udev/hotplug

[Kay Sievers]

On Dec 11, 2007 10:45 PM, Chris Friesen <cfriesen@nortel.com> wrote:
> We're running a 2.6.14 kernel and have a situation where multiple (20 or
> so) ethx devices are being created in about 3 seconds.  This appears to
> cause latency issues for other tasks on the system due to all the
> "/sbin/ifup ethx" processes that get created.
>
> We're seeing these processes being created by udevd directly, by
> /sbin/hotplug, and by /etc/sysconfig/network-scripts/net.hotplug (which
> is in turn created by udevd).
>
> 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. :)

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

Re: many instances of "/sbin/ifup ethx" coming from udev/hotplug

[Chris Friesen]

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?  What's the expected path for ifup to be called in a 
current distro?

Chris

-------------------------------------------------------------------------
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

Re: many instances of "/sbin/ifup ethx" coming from udev/hotplug

[Kay Sievers]

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