Another observation: I still see these messages today after dist- upgrading to container to latest trusty. But *only* with lxc-start, *not* with lxc-start-ephemeral. In the latter case, the job still gets started:
$ sudo status ttyAMA0 ttyAMA0 start/running, process 769 but I don't see the spewage. With "ps aux|grep ttyAMA" I still see the job constantly being respawned, but it doesn't appear at the terminal any more (that might be an LXC quirk/feature/bug, probably unrelated to the cloud image itself). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in 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-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
