Package: systemd-cron Version: 1.3.1+ds1-2 Severity: normal I had @reboot jobs existing, that had already run when my laptop booted. I then installed systemd-cron, and noticed this caused the jobs to run again.
● cron-joey-1.service - [Cron] "@reboot mpd; mpdscribble" Loaded: loaded (/var/spool/cron/crontabs/joey) Active: failed (Result: exit-code) since Sun 2014-10-26 13:52:39 JEST; 14min ago Process: 25218 ExecStart=/bin/sh -c mpd; mpdscribble (code=exited, status=127) Main PID: 25218 (code=exited, status=127) In the example above it didn't matter, but if the @reboot did something expensive, it could be a pain to have it be run at switch time. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-cron depends on: ii init-system-helpers 1.21 ii python 2.7.8-1 pn python:any <none> ii systemd-sysv 215-5+b1 systemd-cron recommends no packages. systemd-cron suggests no packages. -- no debconf information -- see shy jo
signature.asc
Description: Digital signature