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

[Michael Biebl]

Am 17.07.2016 um 18:55 schrieb 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.
>>>
>>
>> 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)
> 
> Looks like we already have a related bug report for jessie:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829537
> 
> Martin, do you think this should be cherry-picked for jessie as well?
> I'm leaning towards yes.

this meaning your fix for getty-static.service


-- 
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/20160717/4aecb650/attachment-0002.sig>