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

[Steffen Neumann]

Hi, we're exactly hit by the problem Vincent described in #40,

This is happened to us on 12.04 and only appeared after an upgrade on 24.9.2012. 
Please see https://lists.ubuntu.com/archives/ubuntu-users/2012-September/264199.html
for some more details.

The problem does not appear on 12.10 anymore, maybe due to the above
mentioned refactoring.

Nevertheless, not being able to run sysctl during network interface configuration 
seems badly broken. Is there a workaround, should this be re-opened or added as a new bug ?

Yours,
Steffen and Paul.

-- 
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:
  Fix Released
Status in “procps” source package in Maverick:
  Fix Committed
Status in “procps” source package in Natty:
  Fix Committed
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