Bug#773252: systemd-timesyncd syncs time about once per minute

2014-12-19 Thread Jos van Wolput
On 12/16/2014 09:31 PM, Michael Biebl wrote: roughly 30s -> 1m, 1m -> 2m, 2m -> 4m, 4m -> 8m ... This looks like a sensible approach to me. As the interval of systemd-timesyncd on my system never increases I have disabled systemd-timesyncd and instead inabled ntp service (/etc/init.d/ntp).

Bug#773269: Computer crash when installing cups-daemon

2014-12-19 Thread Jos van Wolput
On 12/19/2014 09:55 PM, Michael Biebl wrote: It would also help, if you can test with systemd from testing/unstable and the Debian kernel from testing/unstable. Previously I was using kernel 3.18.0 but now 3.18.1 and can't reproduce this issue. As it is not clear in which circumstances this

Bug#773533: efivarfs not mounted by default

2014-12-19 Thread Leif Lindholm
On Fri, Dec 19, 2014 at 04:35:51PM +0100, Michael Biebl wrote: > > Could we build systemd without --disable-efi, please? > > It's probably to late to do that for jessie unless there is some major > breakage caused by that for UEFI systems (which I don't know, not being > familiar with UEFI). Well

Bug#773538: systemd: journal is quite big compared to rsyslog output

2014-12-19 Thread Martin Steigerwald
Hi! So this works nice. After setting "MaxRetentionSec=14day" and restarting "systemd-journald" I get: merkaba:~> du -sch /var/log/* | sort -rh | head -10 348Minsgesamt 143M/var/log/atop 76M /var/log/journal 53M /var/log/collectl 13M /var/log/installer 6,0M/var/log/kern.l

Bug#773538: systemd: journal is quite big compared to rsyslog output

2014-12-19 Thread Martin Steigerwald
Package: systemd Version: 218-2 Severity: normal Dear Maintainer, I have this here: merkaba:~> du -sch /var/log/* | sort -rh | head -10 1,3Ginsgesamt 1,1G/var/log/journal 143M/var/log/atop 53M /var/log/collectl 13M /var/log/installer 6,0M/var/log/kern.log.3.gz 5,9M/va

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Martin Steigerwald
Am Freitag, 19. Dezember 2014, 16:43:38 schrieb Martin Pitt: > Martin Steigerwald [2014-12-19 15:58 +0100]: > > And with that question you dismiss the rest of my bug report? I asked some > > more question. > > Where did Michael say that he dismissed the rest? At least I consider > it a perfectly v

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Martin Steigerwald
Am Freitag, 19. Dezember 2014, 16:39:59 schrieb Michael Biebl: > Am 19.12.2014 um 15:58 schrieb Martin Steigerwald: > > Am Freitag, 19. Dezember 2014, 15:47:28 schrieb Michael Biebl: > >> Am 19.12.2014 um 15:39 schrieb Martin Steigerwald: > >>> Package: systemd > >>> Version: 218-2 > >>> > >>> It

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Martin Pitt
Martin Steigerwald [2014-12-19 15:58 +0100]: > And with that question you dismiss the rest of my bug report? I asked some > more question. Where did Michael say that he dismissed the rest? At least I consider it a perfectly valid bug report (at least until you started swearing). > Still, I want i

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Michael Biebl
Am 19.12.2014 um 15:58 schrieb Martin Steigerwald: > Am Freitag, 19. Dezember 2014, 15:47:28 schrieb Michael Biebl: >> Am 19.12.2014 um 15:39 schrieb Martin Steigerwald: >>> Package: systemd >>> Version: 218-2 >>> >>> It might be nice to place something about this in Jessie releasenotes. >> >> How

Bug#773533: efivarfs not mounted by default

2014-12-19 Thread Michael Biebl
Am 19.12.2014 um 16:19 schrieb Leif Lindholm: > Package: systemd > Severity: normal > > The efivarfs kernel module is built for all UEFI-capable platforms > (i386, amd64, arm64), but since systemd is build with --disable-efi, > the filesystem is not mounted at boot-time on > /sys/firmware/efi/efiv

Bug#773533: efivarfs not mounted by default

2014-12-19 Thread Leif Lindholm
Package: systemd Severity: normal The efivarfs kernel module is built for all UEFI-capable platforms (i386, amd64, arm64), but since systemd is build with --disable-efi, the filesystem is not mounted at boot-time on /sys/firmware/efi/efivars. This makes the efivars package (used by commands like

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Martin Steigerwald
Am Freitag, 19. Dezember 2014, 15:47:28 schrieb Michael Biebl: > Am 19.12.2014 um 15:39 schrieb Martin Steigerwald: > > Package: systemd > > Version: 218-2 > > Severity: normal > > > > Dear Maintainer, > > > > I wondered about the huge lot of audit messages in dmesg and syslog. > > > > The follo

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Michael Biebl
Am 19.12.2014 um 15:39 schrieb Martin Steigerwald: > Package: systemd > Version: 218-2 > Severity: normal > > Dear Maintainer, > > I wondered about the huge lot of audit messages in dmesg and syslog. > > The following is just after a fresh boot: > > merkaba:~> dmesg | grep audit | wc -l > 38 >

Bug#773528: systemd: enables audit without any hint on how to disable it

2014-12-19 Thread Martin Steigerwald
Package: systemd Version: 218-2 Severity: normal Dear Maintainer, I wondered about the huge lot of audit messages in dmesg and syslog. The following is just after a fresh boot: merkaba:~> dmesg | grep audit | wc -l 38 merkaba:~> dmesg | grep audit | grep suppr [ 11.835476] audit_printk_skb: 2

Bug#773269: Computer crash when installing cups-daemon

2014-12-19 Thread Michael Biebl
Am 19.12.2014 um 14:48 schrieb Michael Biebl: > Am 19.12.2014 um 08:32 schrieb Jos van Wolput: >> On 12/19/2014 06:28 AM, Michael Biebl wrote: >>> Please enable persistent logging (see >>> /usr/share/doc/systemd/README.Debian) and/or use something like SSH, >>> which should allow you to access the

Bug#773269: Computer crash when installing cups-daemon

2014-12-19 Thread Michael Biebl
Am 19.12.2014 um 08:32 schrieb Jos van Wolput: > On 12/19/2014 06:28 AM, Michael Biebl wrote: >> Please enable persistent logging (see >> /usr/share/doc/systemd/README.Debian) and/or use something like SSH, >> which should allow you to access the system and then boot the system with >> systemd.log_