I believe that this could work if we launch getty with something like this in
/etc/init/ttyS0.conf :
# ttyS01 - getty
#
# This service maintains a getty on ttyS01 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/ttyS0 -a 2> /dev/null > /dev/null || { stop ; exit 0; }
end script
respawn
script
exec /sbin/getty -L 115200 ttyS01
end script
Without the pre-start, configuring a console on ttyS0 for upstart in
/etc/init/ttyS0.conf for instances that do not have a serial console
present will result in getty repeatedly failing and respawning and the
failures would clutter up /var/log/auth.log with messages like:
Jan 10 21:34:22 test-system getty[1163]: /dev/ttyS0: not a character device
Jan 10 21:34:33 test-system getty[1186]: /dev/ttyS0: not a character device
Jan 10 21:34:43 test-system getty[1200]: /dev/ttyS0: not a character device
Jan 10 21:34:53 test-system getty[1211]: /dev/ttyS0: not a character device
Jan 10 21:35:03 test-system getty[1223]: /dev/ttyS0: not a character device
Jan 10 21:35:13 test-system getty[1235]: /dev/ttyS0: not a character device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220740
Title:
Add a getty/login prompt on ttyS0 cloud images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1220740/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
