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
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
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
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
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
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
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
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
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
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.
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
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.
>
>
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
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
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
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
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
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
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
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
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
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
22 matches
Mail list logo