[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #830693 (http://bugs.debian.org/830693) # Bug title: systemd-container:

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

Am 18.07.2016 um 19:01 schrieb Martin von Wittich: > So as far as I'm concerned, this update can be released. Thanks a lot Martin for the very thorough testing. Very much appreciated. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

Hi, the promised update (I know, I'm a little late): I ran the following two commands on all the servers I listed in my previous mail to count the amount of "BUG" and "Looping too fast" messages in the past 5 days: zgrep Loop

Bug#818978: systemd crashes in lxc on container stop

Michael Biebl [2016-07-18 18:34 +0200]: > Thanks, I'm able to reproduce the problem now on a jessie system with > lxc v2 from backports. > Interestingly, this happens for both a jessie *and* a stretch container. > So it looks like either the combination "v215 host + v230 container" is >

Bug#831691: Please use lxc.haltsignal = SIGRTMIN+3 for systemd containers

Package: lxc Version: 1:2.0.3-1 Severity: normal Hi, he had an interesting discussion today on #pkg-systemd IRC about what modifications are currently done for LXC containers to work properly with systemd. Ideally we'd like to make a default systemd installation work ootb. Atm, the Debian

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#830230: systemd disable wake-on-lan

Christian Hofstaedtler schrieb: > * Norbert Schulz [160714 15:12]: >> output of ethtool eth0 with systemd >> Settings for eth0: > [..] >> MDI-X: on (auto) >> Wake-on: g >> >> output of ethtool eth0 with sysvinit >> Settings for eth0: > [..] >> MDI-X: off

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