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

[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
  - once for eth0
  - once for lo

- The difference between sequential executing (on restarting with /etc/init.d/networking restart) and parallel executing (on rebooting the system).
 The only difference should be the absence of "lo" as state above. My best guess for why you're getting eth0 twice is that of a race condition between the event based bring up and the standard init based bringup.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1126560

Title:
  /etc/networking/* are executed multiple times

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 13.04 dev with ifupdown 0.7.5ubuntu2. I have noticed
  that on booting my system in /etc/networking the scripts in if-pre-
  up.d and if-up.d are executed multiple times. On my observations I
  have noticed that they can even be executed parallelized. I have
  logged what happened on a boot:

  1. The content of /etc/networking/if-pre-up.d is executed parallelized 2 times.
  2. After they have finished the content of /etc/networking/if-up.d is excuted.
  3. Then the content of /etc/networking/if-pre-up.d is excuted again.
  4. At last the content of /etc/networking/if-up.d is executed again too.

  As a summary: The content of /etc/networking/if-pre-up.d was executed
  3times and /etc/networking/if-up.d 2 times.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1126560/+subscriptions