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

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

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

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

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

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

Bug#824779: [pkg-lxc-devel] Bug#824779: container getty-static.service causes lxcfs high cpu usage

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

Bug#824779: [pkg-lxc-devel] Bug#824779: container getty-static.service causes lxcfs high cpu usage

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

Bug#824779: [pkg-lxc-devel] Bug#824779: container getty-static.service causes lxcfs high cpu usage

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

Bug#824779: [pkg-lxc-devel] Bug#824779: container getty-static.service causes lxcfs high cpu usage

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

Bug#824779: [pkg-lxc-devel] Bug#824779: container getty-static.service causes lxcfs high cpu usage

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.

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

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

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

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

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

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.

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

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

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

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

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

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

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

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