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

[Andreas Ntaflos]

Is this now really fixed in Lucid? As I have mentioned in comment #29 we
had applied this update from lucid-proposed and and continue to see this
error in /var/log/boot.log:

init: procps (virtual-filesystems) main process (670) terminated with
status 255

The initial problem remains the same, the sysctl settings do not get
applied in time.

We need to use this workaround in order to get VLAN trunks into Libvirt-
managed virtual machines (KVM):

/etc/rc.local:

# At this point automatic startup of libvirt-bin.conf is disabled, we start it manually below
/sbin/sysctl -p /etc/sysctl.conf
/etc/init.d/networking restart
/etc/init.d/libvirt-bin start
exit 0

This is on Ubuntu 10.04.4, x86_64 on all of our Dell R710 servers.

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