This bug was fixed in the package upstart - 1.4-0ubuntu7
---
upstart (1.4-0ubuntu7) precise; urgency=low
* debian/manpages/upstart-events.7: Added missing events 'container' and
'not-container'.
* Update 'runlevel' event emission time in upstart-events(7) (LP: #921501).
* Merge of important upstream log fixes to avoid spinning when a job
which leaks fds (such as 'sshd -D') is stopped (LP: #926468).
* Merge of lp:~jamesodhunt/upstart/early-job-log-flush to allow jobs that
_end_ very early in the boot to have their output logged.
* debian/conf/flush-early-job-log.conf: Upstart job to force flushing of
early job log output data when disk becomes writeable.
* Re-enable job logging by default.
[ Steve Langasek ]
* init/tests/test_job_process.c: close all fds before running tests that
check for unexpected open fds, so that files leaked from the environment
don't cause the test suite to fail gratuitously. LP: #926473.
* bump debhelper compat to 9 and adjust debian/rules to use the
dpkg-buildflags interfaces, so that upstart can be cross-compiled and
also so we pick up any future hardening flags for free.
-- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 07:52:11 +
** Changed in: upstart (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921501
Title:
runlevel time incorrect in Table 1 of upstart-events(7)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/921501/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
