[Bug 1065684] Re: network-interface-security.conf should be a task

Kees Cook kees at ubuntu.com
Thu Oct 11 21:23:25 UTC 2012


No so simple, unfortunately. Here's why it was written this way:

# In order to handle the lack of upstart feature LP: #568860, we need to
# run multiple times, for each of the above "starting" service instances, or
# else another one might run while we're running, and not wait for us to
# finish.
instance $JOB${INTERFACE:+/}${INTERFACE:-}

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

Title:
  network-interface-security.conf should be a task

Status in “ifupdown” package in Ubuntu:
  Confirmed

Bug description:
  The network-interface-security upstart job should be a task.  It
  doesn't do anything after the pre-start script, and there is no stop
  on.  On a machine which creates (and destroys) a lot of interfaces,
  this can result in thousands of network-interface-security jobs for
  non-existent nics.

  THis is related to bug 1065589.

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




More information about the foundations-bugs mailing list