Bug#850435: starts daily, weekly, monthly targets at midnight

2017-01-06 Thread Marc Haber
Package: systemd-cron Version: 1.5.4-2 Severity: wishlist Dear Maintainer, thanks for providing this compatibility layer to help transition from a cron daemon to systemd timers. Using run-parts in the .service units prevents all items of a daily|weekly|monthly cron job from starting at once. How

Bug#850435: starts daily, weekly, monthly targets at midnight

2017-01-06 Thread Julian Andres Klode
On Fri, Jan 06, 2017 at 02:29:19PM +0100, Marc Haber wrote: > Package: systemd-cron > Version: 1.5.4-2 > Severity: wishlist > > Dear Maintainer, > > thanks for providing this compatibility layer to help transition from > a cron daemon to systemd timers. Using run-parts in the .service units > pre

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

2017-01-06 Thread Julian Andres Klode
Second ping, more than 2 years later. Seriously, that's more than 2 years old now, with a simple workaround, and security implications (private data remaining accessible after logout). On Sat, Oct 18, 2014 at 09:13:05PM +0200, Julian Andres Klode wrote: > (adding pkg-systemd-maintainers@lists.ali

Bug#850436: mounting var at boot: Mount point is not empty

2017-01-06 Thread Daniel Pocock
Package: systemd Version: 215-17+deb8u5 When my system is booting, I see the following: systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway. -- Subject: Mount point is not empty -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd

Bug#850436: mounting var at boot: Mount point is not empty

2017-01-06 Thread Michael Biebl
Am 06.01.2017 um 15:12 schrieb Daniel Pocock: > root-fs/var/lib/systemd/random-seed > root-fs/var/log/unattended-upgrades/unattended-upgrades-shutdown.log > root-fs/var/run/avahi-daemon > root-fs/var/run/unattended-upgrades.lock Do you know, when those files are created? E.g. systemd-random-s

Bug#850435: starts daily, weekly, monthly targets at midnight

2017-01-06 Thread Alexandre Detiste
Hi, I have a different proposal upstream that propose to get rid of run-parts completely. https://github.com/systemd-cron/systemd-cron/issues/47 I like it in some ways because run-parts gets in the way of proper logging (it's exit-code is max of all process exit codes, error-mail is useless & one

Bug#850435: starts daily, weekly, monthly targets at midnight

2017-01-06 Thread Marc Haber
Hi, On Fri, Jan 06, 2017 at 03:33:12PM +0100, Alexandre Detiste wrote: > I have a different proposal upstream that propose to get rid of > run-parts completely. > https://github.com/systemd-cron/systemd-cron/issues/47 As long as the jobs still run in a predictable order and serialized, I don't ca

Bug#850435: starts daily, weekly, monthly targets at midnight

2017-01-06 Thread Marc Haber
On Fri, Jan 06, 2017 at 03:03:44PM +0100, Julian Andres Klode wrote: > On Fri, Jan 06, 2017 at 02:29:19PM +0100, Marc Haber wrote: > > However, daily|weekly|monthly are started together at midnight, while > > the classic crond/anacron setup starts them in a staggered way which > > helps keeping the

Bug#850447: systemd backport sections only 4K aligned, won't boot with arm64 64K kernel

2017-01-06 Thread James Morse
Package: systemd Version: 230-7~bpo8+2 Severity: normal Hi, This version of systemd won't boot on arm64 when the kernel is configured for 64K pages: > Starting init: /etc/init exists but couldn't execute it (error -13) > Starting init: /bin/sh exists but couldn't execute it (error -14) > Kernel p

Processed: tagging 850447

2017-01-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 850447 + moreinfo Bug #850447 [systemd] systemd backport sections only 4K aligned, won't boot with arm64 64K kernel Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 850447: http://bugs.

Bug#850447: systemd backport sections only 4K aligned, won't boot with arm64 64K kernel

2017-01-06 Thread Michael Biebl
Hi James, thanks for your bug report. Am 06.01.2017 um 17:06 schrieb James Morse: > > This version of systemd won't boot on arm64 when the kernel is configured for > 64K pages: Is this the case for the Debian provided arm64 kernels? > This is potentially a wider issue affecting anything else b

Bug#849579: systemd-analyze includes previous uptime when using efi + grub2 after systemctl reboot

2017-01-06 Thread Michael Biebl
On Wed, 28 Dec 2016 16:40:50 -0500 Asara wrote: > Package: systemd > Version: 232-8 > Severity: minor > Tags: upstream > > Dear Maintainer, > It seems as if when rebooting a machine running with efi, > systemd-analyze seems to include the previous uptime as > in the 'firmware' section. > >

systemd_215-17+deb8u6_amd64.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

2017-01-06 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Dec 2016 21:33:51 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal

Bug#839607: marked as done (Robustify manager_dispatch_notify_fd())

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#839607: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #839607, regarding Robustify manager_dispatch_notify_fd() to be marked as done. This means that you claim that the problem has been dealt

Bug#777348: marked as done (shutdown: handle unknown options more gracefully)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#776997: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #776997, regarding shutdown: handle unknown options more gracefully to be marked as done. This means that you claim that the problem has

Bug#776997: marked as done (shutdown: handle unknown options more gracefully)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#776997: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #776997, regarding shutdown: handle unknown options more gracefully to be marked as done. This means that you claim that the problem has

Bug#774153: marked as done (systemd-tty-ask-password hangs udev postinst until daemon-reexec is run)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#774153: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #774153, regarding systemd-tty-ask-password hangs udev postinst until daemon-reexec is run to be marked as done. This means that you cla

Bug#833849: marked as done (systemd: localed fails to start if /etc/default/keyboard is missing)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#833849: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #833849, regarding systemd: localed fails to start if /etc/default/keyboard is missing to be marked as done. This means that you claim th

Bug#778802: marked as done (shutdown: handle unknown options more gracefully)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#776997: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #776997, regarding shutdown: handle unknown options more gracefully to be marked as done. This means that you claim that the problem has

Bug#818978: marked as done (systemd crashes in lxc on container stop)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#818978: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #818978, regarding systemd crashes in lxc on container stop to be marked as done. This means that you claim that the problem has been dea

Bug#819314: marked as done (procps: [sysctl] Missing dependency when used with systemd)

2017-01-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 21:17:47 + with message-id and subject line Bug#819314: fixed in systemd 215-17+deb8u6 has caused the Debian Bug report #819314, regarding procps: [sysctl] Missing dependency when used with systemd to be marked as done. This means that you claim that the pr

Bug#800707: systemd: Sytem hangs on shutdown when nfs-shares are mounted via autofs

2017-01-06 Thread Wolf-Dieter Groll
Dear Maintainer, I just encountered the same problem after upgrading two laptops from Xubuntu 14.04 LTS to the actual version of Debian Jessie. One running the i386 version, the other amd64. With Xubuntu autofs worked smoothly, but since the upgrade to jessie shutdown fails as long as there are a