Yes, I never thought of it as an LXC bug in the first place. Whatever installs that job (cloud-init? our cloud image build process?) ought to change the upstart job to only start up if such a device exists in the first place.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
