sysvinit would have presented a problem if its configuration file got
corrupted

upstart did behave badly, it shouldn't have entered an infinite loop,
I've just fixed that bug by ensuring that it doesn't generate the
"stalled"  event if there's nothing started by it.

** Changed in: upstart (Ubuntu)
       Status: Confirmed => Fix Committed

-- 
spins when stalled and no job handles stalled event
https://launchpad.net/bugs/59170

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to