touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #38836
[Bug 771372] Re: procps runs too early in the boot process
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as "Won't Fix".
** Changed in: procps (Ubuntu Maverick)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Won't Fix
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