This bug was fixed in the package lxc - 0.7.5-3ubuntu18 --------------- lxc (0.7.5-3ubuntu18) precise; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will proceed. (LP: #924337) * 0034-fix-lxc-execute-reboot.patch: fix bad handling of 'exit 0' for lxc-execute introduced with the container reboot handling. (LP: #927863) * debian/lxcguest.lxcmount.upstart: add '--no-wait' to emit to make sure we don't wait for the event to be processed. * 0035-lxc-init-ignore-shm.patch: if lxc-init can't mount /dev/shm, don't fail on account of that. (LP: #927883) * debian/lxc.init: if the network is already up, exit before setting the trap EXIT. -- Serge Hallyn <serge.hal...@ubuntu.com> Mon, 06 Feb 2012 17:37:37 -0600 ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/927863 Title: container reboot patch broke clean lxc-execute exits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/927863/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs