Package: systemd-cron
Version: 1.1.1-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I had install systemd back in mid-Feb--had not checked logs until last week. I
found that cron jobs were not being run.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I manually installed the newer systemd-cron package from upstream (1.21) &
corrected it to work with my system. This started to make cron jobs work. My
logs indicated that "/user/bin/run-parts" were not found, so jobs were not
run.
I then created a link from /bin/run-parts to /usr/bin/run-parts which was the
final piece of the puzzle.
* What was the outcome of this action?
Cron jobs are now running normally.
* What outcome did you expect instead?
Expected version 1.1.1-1 to run cron jobs normally.
I can be contacted to show what I did to make the cron.target(s) run - the
changes were very minimal.
I run a sid system & pull from experimental were it looks like it would be
helpful.
-- System Information:
Debian Release: jessie/sid
APT prefers experimental
APT policy: (900, 'experimental'), (900, 'unstable'), (850, 'testing'), (500,
'testing-updates'), (500, 'testing-proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/8 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.18
ii systemd 204-8
systemd-cron recommends no packages.
systemd-cron suggests no packages.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
