Bug#1051805: systemd-cron: shell redirect not working in crontab entries

[Alexandre Detiste]

> And this is moot anyway since we only inline single-word programs,
> so we could only do this transformation for single-word programs.
> I cannot imagine anything that would be affected if we do /that/,
> since there aren't any programs that are useful when you run them with
> no arguments from a crontab /and/ you're managing them like that.

I do.

When someone has an existing working script
in /etc/cron.{hourly|daily|weekly|monthly}
and only need to tweek the _schedule_
(or localy the CRON_MAIL_SUCCESS);
it will turn up as a such "command without argument".

$ crontab  -l
# min hour dom month dow command
CRON_MAIL_SUCCESS=never
@hourly ~/bin/budget.py
@daily ~/bin/graph.py
@daily ~/bin/git_updater.sh
@daily ~/bin/babel.sh

I merged 75% of the MR
and made a new version.

Hope this further stabilizes.

Thanks