[Bug 1273205] [NEW] /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist

[Martin Pitt]

Public bug reported:

I created an LXC container with the current armhf cloud images on a
Calxeda node. Due to /etc/init/ttyAMA0.conf, I get these lines written
into the terminal every few seconds:

<4>init: ttyAMA0 main process (3035) terminated with status 1
<4>init: ttyAMA0 main process ended, respawning

This makes working in a terminal rather hard and also clutters logs. Can
the job please be fixed to only start up if there actually is a
/dev/ttyAMA*?

$ uname -a
Linux trusty-cloud 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:18:34 UTC 2013 armv7l armv7l armv7l GNU/Linux
$ ls -l /dev/ttyA*
ls: cannot access /dev/ttyA*: No such file or directory

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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