Thanks for reporting this issue. However, the console device is a device
expected to exist on all Linux systems. The problem here is that Upstart
*needs* access to the console: if it has no console access, jobs would
behave differently in an OpenVZ container to running outside a container
(bad). The patch above will not help jobs that have specified they want
console access or ownership ("console output" or "console owner").I am not an OpenVZ expert, but I do feel that the "fix" for this issue is for the OpenVZ environment to provide a /dev/console that Upstart is able to use such as would be provided by other virtualization technologies (LXC, qemu/kvm, Xen, VirtualBox) otherwise Upstart cannot guarantee job behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880049 Title: 100% CPU usage in init if /dev/console is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/880049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
