Manual configuration of the getty service is no longer required for
Trusty or later. The system-specific "console=ttySX" parameter in
/proc/cmdline is enough to configure the SOL tty during Ubuntu
installation.
See http://tracker.ceph.com/issues/15269 for further explanation.
Signed-off-by: David Galloway <dgallowa@redhat.com>
name: cron
state: restarted
-- name: start ttyS1
- service:
- name: ttyS1
- state: started
-
-- name: start ttyS2
- service:
- name: ttyS2
- state: started
-
- name: restart nagios-nrpe-server
service:
name: "{{ nrpe_service_name }}"
tags:
- kernel_logging
-- name: Upload ttyS1.conf.
- template:
- src: ttyS1.conf
- dest: /etc/init/ttyS1.conf
- owner: root
- group: root
- mode: 0644
- notify:
- - start ttyS1
- when: not ansible_hostname | search("^target")
-
-# this only runs on mira nodes
-- name: Upload ttyS2.conf.
- template:
- src: ttyS2.conf
- dest: /etc/init/ttyS2.conf
- owner: root
- group: root
- mode: 0644
- notify:
- - start ttyS2
- when: ansible_hostname | search("^mira*")
-
- name: Enable kernel modules to load at boot time.
template:
src: modules
+++ /dev/null
-# {{ ansible_managed }}
-# ttyS1 - getty
-#
-# This service maintains a getty on ttyS1 from the point the system is
-# started until it is shut down again.
-
-start on stopped rc RUNLEVEL=[2345]
-stop on runlevel [!2345]
-
-respawn
-exec /sbin/getty -8 115200 ttyS1
+++ /dev/null
-# {{ ansible_managed }}
-# ttyS2 - getty
-#
-# This service maintains a getty on ttyS2 from the point the system is
-# started until it is shut down again.
-
-start on stopped rc RUNLEVEL=[2345]
-stop on runlevel [!2345]
-
-respawn
-exec /sbin/getty -8 115200 ttyS2