Your message dated Mon, 28 Jul 2014 15:09:47 +1000 with message-id <20140728050945.GA5699@frey> and subject line 744828 does not apply to Debian has caused the Debian Bug report #744828, regarding systemd-cron not running cron jobs. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 744828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744828 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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.
--- End Message ---
--- Begin Message ---Upstream defaults to /usr/bin/run-parts. Debian's packaging correctly passes --runparts=/bin/run-parts to ./configure. The resulting package as at 1.1.1-1 is correct: cron-daily.service:9: ExecStart=/bin/run-parts /etc/cron.daily cron-hourly.service:9: ExecStart=/bin/run-parts /etc/cron.hourly cron-monthly.service:9: ExecStart=/bin/run-parts /etc/cron.monthly cron-weekly.service:9: ExecStart=/bin/run-parts /etc/cron.weekly Dean wrote: > I manually installed [systemd-cron 1.21] from upstream. Clearly Dean simply forgot to pass this option.
signature.asc
Description: Digital signature
--- End Message ---
