Bug#866313: systemd: create /var/log/lastlog if it does not exist

2017-06-28 Thread Peter Colberg
Hi Michael, On Wed, Jun 28, 2017 at 10:10:25PM +0200, Michael Biebl wrote: > Am 28.06.2017 um 21:50 schrieb Peter Colberg: > > Package: systemd > > Version: 233-9 > > Severity: normal > > > > Dear Maintainer, > > > > Could you extend /usr/lib/tmpfil

Bug#866313: systemd: create /var/log/lastlog if it does not exist

2017-06-28 Thread Peter Colberg
Package: systemd Version: 233-9 Severity: normal Dear Maintainer, Could you extend /usr/lib/tmpfiles.d/var.conf as follows? f /var/log/lastlog 0664 root utmp - systemd already creates /var/log/wtmp and /var/log/btmp if they do not exist. For custom live-boot images that exclude files under /var

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-12 Thread Peter Colberg
On Fri, Feb 13, 2015 at 08:02:09AM +0100, Michael Biebl wrote: > Am 13.02.2015 um 07:44 schrieb Michael Biebl: > > I went on and looked what the watchdog package does. Interestingly, it > > clamps any timeout value to 254s, thus not hitting this issue. > > Apparently, i6300esb is able to deal with

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-12 Thread Peter Colberg
On Thu, Feb 12, 2015 at 08:50:59AM +0100, Michael Biebl wrote: > Some more findings: Aside from only happening on reboot, but not > shutdown, it also seems to only happen with i6300esb. Switching the qemu > config to use ib700 instead of i6300esb, I am not able to trigger the > problem. This confir

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-11 Thread Peter Colberg
On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote: > Thanks, I was able to reproduce the issue this way (marking the bug > accordingly). > It's likely that the watchog is resetting systemd/rsyslog before it has > a chance to stop properly. > > Let's see, where we can go from here. In

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-11 Thread Peter Colberg
On Thu, Feb 12, 2015 at 05:44:59AM +0100, Michael Biebl wrote: > Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from > [1], started it with "qemu-system-x86_64 -enable-kvm -hda > debian_wheezy_amd64_standard.qcow2". > Then did a dist-upgrade to jessie, which replaced sysvinit w

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-11 Thread Peter Colberg
On Thu, Feb 12, 2015 at 04:28:38AM +0100, Michael Biebl wrote: > Just to be clear here: Is this only happening once after the > dist-upgrade from wheezy (sysvinit) to jessie (systemd-sysv) on reboot > or everytime you reboot your jessie system? It happens everytime I reboot from within the VM. >

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

2015-02-11 Thread Peter Colberg
Package: systemd Version: 215-11 Severity: grave Justification: causes non-serious data loss Dear Maintainer, After upgrading to jessie from wheezy, I noticed that some of the system logs experience corruption when rebooting the system. After rebooting the system using the command ‘reboot’ or ‘s