[Bug 771372] Re: procps runs too early in the boot process

[Steve Langasek]

Simon,

> This does not work on my Lucid. The sysctl settings related to
> the bridge modules are not set to the values defined under
> /etc/sysctl.d/60-bridge-firewalling.conf.

Oh.  Well, that's actually perfectly understandable, because the static-
network-up event was only introduced in oneiric!

James, that means we need a different fix here for lucid/maverick/natty.
Can you give this a think?

** Changed in: procps (Ubuntu Lucid)
       Status: Fix Committed => Triaged

** Changed in: procps (Ubuntu Lucid)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Changed in: procps (Ubuntu Maverick)
       Status: In Progress => Triaged

** Changed in: procps (Ubuntu Maverick)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Changed in: procps (Ubuntu Natty)
       Status: Fix Committed => Triaged

** Changed in: procps (Ubuntu Natty)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

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

Title:
  procps runs too early in the boot process

Status in “procps” package in Ubuntu:
  Fix Released
Status in “procps” source package in Lucid:
  Triaged
Status in “procps” source package in Maverick:
  Triaged
Status in “procps” source package in Natty:
  Triaged
Status in “procps” source package in Oneiric:
  Fix Committed
Status in “procps” source package in Precise:
  Fix Released

Bug description:
  Binary package hint: upstart

  The start on criteria is for procps.conf is:
  start on virtual-filesystems

  This runs before some kernel modules are loaded, and procps applies
  the settings before they "exist", this is most noticed with network
  and network-related jobs (nfs, bridge).

  This bug may be considered a duplicate of LP Bug #690433.  I am
  opening a new one anyway, however because I think it's worth
  considering a more robust solution that would work for any possible
  kernel module.

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