get_started is a job that also specifes 'start on started', so upstart
was chasing both jobs constantly: only 1 job can reasonably specify such
an unspecific start condition.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197426
Title:
starpar-upstart-inject causes upstart to consume a lot of cpu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1197426/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
