Bug#824816: dh-systemd: systemd2init doesn't convert exec fields with arguments correctly

2016-05-19 Thread Phil
Package: dh-systemd Version: 1.33 Severity: normal Dear Maintainer, Running systemd2init on a systemd unit file that has arguments on exec fields will create incorrect values in the output file. As an example, when the unit file contains: ExecStartPre=/bin/foo -z bar -y baz -x qux The .init fil

Bug#824813: dh-systemd: systemd2init always falls back to default values

2016-05-19 Thread Phil
Package: dh-systemd Version: 1.33 Severity: normal Tags: patch Dear Maintainer, The .init file produced by systemd2init always has default values for every field, EG. DESC= and DAEMON=/usr/sbin/\$NAME This appears to be caused by the script (via augtool) checking 2 non-existing locations for the

Bug#824804: update-rc.d: may invoke insserv without -f flag when initscripts is installed but not configured

2016-05-19 Thread Felipe Sateler
X-Debbugs-Cc: andr...@fatal.se Package: init-system-helpers Version: 1.33 Severity: normal Filing so that this is tracked somewhere. update-rc.d currently has support for invoking insserv with the -f flag, to allow initscripts-less installations. This should allow packages to drop dependencies on

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

2016-05-19 Thread Manuel Bilderbeek
Hi, On 19-05-16 23:04, Michael Biebl wrote: Looks like I need to have systemd-timesync run *before* systemd-fsck!? If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options] broken_system_clock=1 (as referenced in my earlier reply) is an option. Can you try that?

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

2016-05-19 Thread Michael Biebl
Am 19.05.2016 um 21:30 schrieb Manuel Bilderbeek: > > -- Logs begin at ma 2028-05-22 12:37:10 CEST, end at do 2016-05-19 > 21:22:23 CEST. -- > > Looks like I need to have systemd-timesync run *before* systemd-fsck!? If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options]

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

2016-05-19 Thread Manuel Bilderbeek
Hi, Thanks for taking interest in this annoying problem. Today I again got an fsck at boot... On 18-05-16 23:35, Michael Biebl wrote: fsck.ext[234] should no longer run an fsck because of that. Which version of e2fsprogs have you installed? Should be latest in testing: ii e2fsprogs

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Michael Biebl
Am 19.05.2016 um 18:29 schrieb Ansgar Burchardt: > On Thu, 2016-05-19 at 18:27 +0200, Michael Biebl wrote: >> Could we add the Important: yes field to "init"? Having that makes a >> lot of sense to me. > > To init or to its dependencies (systemd-sysv, sysvinit-core)? The > latter would not only w

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Michael Biebl
Am 19.05.2016 um 18:27 schrieb Michael Biebl: > Am 19.05.2016 um 18:11 schrieb Martin Pitt: >> >>> - Now: >>>+ "init" package: Remove "Essential: yes" >>>+ "init-system-helpers" package: Add "Essential: yes" >>> - Later: >>>+ "init": Change priority from "required" to "important". >>

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Ansgar Burchardt
On Thu, 2016-05-19 at 18:27 +0200, Michael Biebl wrote: > Could we add the Important: yes field to "init"? Having that makes a > lot of sense to me. To init or to its dependencies (systemd-sysv, sysvinit-core)?  The latter would not only warn when uninstalling all init systems, but also when switc

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Michael Biebl
Am 19.05.2016 um 18:11 schrieb Martin Pitt: > Control: tag -1 pending > > Hello all, > > Ansgar Burchardt [2016-05-05 15:05 +0200]: >> I would like "init" to be optional in Debian 9 for chroot environments >> and some uses of containers. A first step seems to be making "init" no >> longer essent

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Ansgar Burchardt
Hi, On Thu, 2016-05-19 at 18:11 +0200, Martin Pitt wrote: > > And do we miss anything for the priority change after that (besides > > confirming with d-boot@)? > Would you mind starting the discussion on d-boot for that? I would like to wait a few more days (until the next d-i alpha currently in

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Martin Pitt
Control: tag -1 pending Hello all, Ansgar Burchardt [2016-05-05 15:05 +0200]: > I would like "init" to be optional in Debian 9 for chroot environments > and some uses of containers. A first step seems to be making "init" no > longer essential; it would nice nice if the priority could later be >

Processed: Re: Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

2016-05-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #756023 [init] init: Move "Essential: yes" from init to init-system-helpers Bug #823501 [init] init: move "Essential: yes" from init to init-system-helpers Added tag(s) pending. Added tag(s) pending. -- 756023: http://bugs.debian.org/cgi-bin/bugr

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

2016-05-19 Thread Wang Jian
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