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

[Colin Watson]

I think the problem is that the procps postinst in maverick uses 'start
procps' rather than 'invoke-rc.d procps start || exit $?' as is used in
precise.  See bug 602896 for the fix.

This is a pre-existing bug in maverick, but it was dormant because the
installer didn't need to upgrade procps in this phase of installation
until now.  I think the fix for bug 602896 needs to be backported to
maverick-proposed.  This bug was fixed in natty, and, oddly, lucid
didn't suffer from it in the first place because it doesn't appear to
start the procps job in the postinst at all.

** Tags added: verification-failed-maverick

-- 
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 Committed
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