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

[Launchpad Bug Tracker]

This bug was fixed in the package procps - 1:3.2.8-11ubuntu2

---------------
procps (1:3.2.8-11ubuntu2) precise; urgency=low

  * Make procps job run twice: as early as possible (for kernel
    parameters such as kernel.printk) and then after all network
    interfaces are up (to account for any kernel parameters relating
    to recently loaded networking modules) (LP: #771372).
 -- James Hunt <james.hunt at ubuntu.com>   Wed, 16 Nov 2011 15:17:38 +0000

** Changed in: procps (Ubuntu Precise)
       Status: Triaged => Fix Released

-- 
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:
  Triaged
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