On 10/11/2012 03:18 PM, Dan Kegel wrote: > On Thu, Oct 11, 2012 at 12:16 PM, Serge Hallyn > <serge.hal...@canonical.com> wrote: >> Thanks, Dan. I've reproduced it and commented in the bug. It's not >> really a bug in lxc. I at least when the veth is destroyed a uevent >> should be sent saying net-device-removed. Still digging/thinking. > > Now I know I'm an early adopter :-)
Odd that I didn't notice that before, I indeed have several thousands of those on my servers ;) Anyway, it's not going to impact the performance or cause any real effect besides polluting upstart's instance list. Even though I could (with my ifupdown maintainer hack on) fix the upstart job to ignore veth, it's not really the right solution, as Serge said, I think the right way of handling that would be to get a net-device-removed even from udev when moving a veth device inside the container. -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
