[Bug 1126560] Re: /etc/networking/* are executed multiple times

2014-03-20 Thread Stéphane Graber
** Changed in: ifupdown (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126560 Title: /etc/networking/* are executed multiple times To manage notifications

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
--all does not explain why 2 interfaces in /etc/network/interfaces marked as auto are causing 3 starts of network devices. ** Changed in: ifupdown (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
I have now extended my script with $IFACE and the result is very annoying. On restarting the network with /etc/init.d/networking restart (network_restart2.log) --all and eth0 were registered. I'm wondering why eth0 is registered there if --all is already used or why lo is missing. On rebooting the

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
** Attachment added: network_reboot2.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+attachment/3552579/+files/network_reboot2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
** Attachment added: network_restart2.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+attachment/3552580/+files/network_restart2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Stéphane Graber
From the manpage: When ifupdown is being called with the --all option, before doing anything to interfaces, if calls all the hook scripts (pre-up or down) with IFACE set to --all, LOGICAL set to the current value of --allow parameter (or auto if it's not set), ADDRFAM=meta

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
This does not explain: - Why lo is missing on /etc/init.d/networking restart. - Why eth0 was registered 2 times (if-pre-up.d) on rebooting. - The difference between sequential executing (on restarting with /etc/init.d/networking restart) and parallel executing (on rebooting the system). **

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Stéphane Graber
- Why lo is missing on /etc/init.d/networking restart. - Because we never bring down lo on networking restart. - Why eth0 was registered 2 times (if-pre-up.d) on rebooting. No idea and I can't reproduce this here. Here I see the pre-up scripts being called 3 times: - once for --all -

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Sworddragon
Maybe there is a problem with an upstart script or something else. But what is now the correct behavior? The sequential or parallel executing? Maybe the parallelization comes from upstart too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-03-01 Thread Stéphane Graber
both are the correct behaviour. Most interfaces are brought up through udev events as soon as the kernel finds them, however the standard sequential bring up is still there for the few cases where we fail to get kernel events. Those cases include ethX interfaces in containers, tunnel devices,

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-28 Thread Andrew Shadura
This is fine, not a bug :) Read the man page regarding --all. ** Changed in: ifupdown (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126560 Title:

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-17 Thread Sworddragon
Interfaces are brought up as they show up from the kernel, so they can indeed be brought up in parallel. I have tested this and it seems to be false (assuming there is a bug on booting). I have written a script which helps me debugging this problem and placed it in /etc/network/if-pre-up.d/ and

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-17 Thread Sworddragon
** Attachment added: network_reboot.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+attachment/3533750/+files/network_reboot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-17 Thread Sworddragon
** Attachment added: network_restart.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+attachment/3533751/+files/network_restart.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-15 Thread Stéphane Graber
Please attach your /etc/network/interfaces ** Changed in: ifupdown (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126560 Title: /etc/networking/* are

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-15 Thread Sworddragon
** Attachment added: interfaces https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+attachment/3530718/+files/interfaces ** Changed in: ifupdown (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1126560] Re: /etc/networking/* are executed multiple times

2013-02-15 Thread Stéphane Graber
Ok, with that config you should have all the scripts run twice in theory, once for the loopback device and once for eth0. Not sure why you're seeing one running 3 times though. All the .d scripts are run once per interface, so it's perfectly normal for them to be called multiple times.