Bug#824779: container getty-static.service causes lxcfs high cpu usage

[Wang Jian]

Package: systemd
Version: 229-5
Severity: normal

getty-static.service starts getty on tty2-6, but container has only 4
ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
This leads to high cpu usage on host's lxcfs daemon.

In container (debian jessie container on debian jessie host)
--/lib/systemd/system/getty-static.service--
[Unit]
Description=getty on tty2-tty6 if dbus and logind are not available
ConditionPathExists=/dev/tty2
ConditionPathExists=!/lib/systemd/system/dbus.service

[Service]
Type=oneshot
ExecStart=/bin/systemctl --no-block start getty at tty2.service
getty at tty3.service getty at tty4.service getty at tty5.service
getty at tty6.service
RemainAfterExit=true
--/lib/systemd/system/getty-static.service--

--/usr/share/lxc/config/common.conf--
lxc.tty = 4
--/usr/share/lxc/config/common.conf--

Because tty2-tty6 is hardcoded in getty-static.service as above in
spite that systemd-getty-generator generates service for tty1-tty4
corretly, I prefer that this is a bug of systemd.