[Bug 771372] Re: procps runs too early in the boot process
Martin Pitt
martin.pitt at ubuntu.com
Thu Nov 17 05:06:32 UTC 2011
Under the new precise egide of reverting broken uploads if they don't
make the situation worse, I did that now.
procps (1:3.2.8-11ubuntu3) precise; urgency=low
* debian/upstart: Revert previous upload, breaks upgrades. (LP:
#891369)
-- Martin Pitt <martin.pitt at ubuntu.com> Thu, 17 Nov 2011 06:04:10
+0100
** Changed in: procps (Ubuntu Precise)
Status: Fix Released => Triaged
--
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:
Triaged
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:
Triaged
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
More information about the foundations-bugs
mailing list