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

[Michael Biebl]

On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt <mpitt at debian.org> wrote:
> Control: tag -1 pending
> 
> Wang Jian [2016-05-19 23:59 +0800]:
> > 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.
> > 

That's interesting. Shouldn't the rate liming of systemd kick in here?

Can you show us the output of systemctl status getty at tty5.service and/or
getty at tty6.service

> There is no point in even wasting four getty processes on tty1-4 in
> LXC -- containers are not meant to have gettys on ttys in the first
> place. I committed a fix to git for that.
> (ConditionVirtualization=!container)

getty-static.service is really simplistic. Maybe we should replace it by
a tiny generator which runs in case dbus is not installed and creates
symlink in /run/systemd/generator/getty.target.wants/
 for actually available ttys. We could even make it respect it NAutoVTs=
from logind.conf then.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160719/f7e57dbf/attachment-0002.sig>