[Bug 771372] Re: procps runs too early in the boot process
Tobin Davis
771372 at bugs.launchpad.net
Mon Dec 5 22:10:35 UTC 2011
Full syslog of the failing install on amd64.
** Attachment added: "maverick-amd64.syslog"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/+attachment/2621063/+files/maverick-amd64.syslog
--
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
More information about the foundations-bugs
mailing list