The problem can be mitigated by deleting /etc/init/ttyAMA0.conf or
editing to contain the following:
# ttyAMA0 - getty
#
# This service maintains a getty on ttyAMA0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)
stop on runlevel [!2345]
pre-start script
# getty will not be started if the serial console is not present
stty -F /dev/ttyAMA0 -a 2> /dev/null > /dev/null || { stop ; exit 0; }
end script
respawn
script
exec /sbin/getty -L ttyAMA0 115200 vt102
end script
# written by cloud image build process
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-13.04-month-5
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-13.04-month-5 => None
** Changed in: cloud-init (Ubuntu)
Milestone: None => raring-updates
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
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
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
