Am 20.07.2016 um 17:37 schrieb Wang Jian:
> # diff -u /lib/systemd/system/getty@.service
> /etc/systemd/system/getty@.service
> --- /lib/systemd/system/getty@.service 2016-04-25 17:32:15.0 +0800
> +++ /etc/systemd/system/getty@.service 2015-05-17 20:28:50.253964583 +0800
> @@ -21,7 +21,
Am 19.07.2016 um 14:12 schrieb Michael Biebl:
> On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Given Lennarts explanation at [1], I would suggest that we replace that
> condition with ConditionPathExists=/dev/tty0
There is an interesting follow-up by Lennart regarding LXC and ttys
http
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt 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 u
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt 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 u
On Mon, 18 Jul 2016 11:05:12 +0200 Michael Biebl wrote:
> Am 18.07.2016 um 07:56 schrieb Evgeni Golov:
> > Hi again,
> >
> > On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
> > wrt SIGPWR: iirc lxc-stop will issue SIGPWR to the container to stop it,
> > and this was needed to prop
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt 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 u
Am 18.07.2016 um 09:05 schrieb Evgeni Golov:
> On Mon, Jul 18, 2016 at 07:56:40AM +0200, Martin Pitt wrote:
>> Hello Michael, Evgeni,
>>
>> Evgeni Golov [2016-07-18 7:25 +0200]:
> There is no point in even wasting four getty processes on tty1-4 in
> LXC -- containers are not meant to have
Am 18.07.2016 um 07:56 schrieb Evgeni Golov:
> Hi again,
>
> On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
>>> I assume this file was created by lxc.
>>> Apparently the lxc maintainers decided it is useful to have a getty on
>>> tty1-tty4? lxc maintainers, could you give us some i
On Mon, Jul 18, 2016 at 07:56:40AM +0200, Martin Pitt wrote:
> Hello Michael, Evgeni,
>
> Evgeni Golov [2016-07-18 7:25 +0200]:
> > > > 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
Hi again,
On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
> > I assume this file was created by lxc.
> > Apparently the lxc maintainers decided it is useful to have a getty on
> > tty1-tty4? lxc maintainers, could you give us some input here, why
> > getty-static.service was not com
Hello Michael, Evgeni,
Evgeni Golov [2016-07-18 7:25 +0200]:
> > > 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=!containe
Hi Michael,
On Mon, Jul 18, 2016 at 12:17:27AM +0200, Michael Biebl wrote:
> Am 16.07.2016 um 15:34 schrieb Martin Pitt:
> > 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. g
Am 18.07.2016 um 00:17 schrieb Michael Biebl:
> Am 16.07.2016 um 15:34 schrieb Martin Pitt:
>> 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
Am 16.07.2016 um 15:34 schrieb Martin Pitt:
> 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
Hello Michael,
Michael Biebl [2016-07-17 18:55 +0200]:
> 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.
I agree. Technicall
Am 17.07.2016 um 18:55 schrieb Michael Biebl:
> On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt 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 res
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt 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 u
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
Processing control commands:
> tag -1 pending
Bug #824779 [systemd] container getty-static.service causes lxcfs high cpu usage
Added tag(s) pending.
--
824779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
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
20 matches
Mail list logo