On 21 Mar 2016 09:23, "Alexandre Detiste" <[email protected]> wrote: > > 2016-03-21 12:54 GMT+01:00 Felipe Sateler <[email protected]>: > > > > > [Service] > > > Type=oneshot > > > IgnoreSIGPIPE=false > > > ExecStart=foo > > > > Is this the real output from systemd-cron? > > > No > > > > > Then it should be fixed: > > > > 1. Exec* need their first argument to be a full path. > > 2. Exec* are not executed via a shell. IIRC, crontab lines can include > > shell constructs. Systemd-cron should generate units that use a shell > > (eg, /bin/sh -c 'foo'). > > If the job is a full path (eg /usr/local/bin/<something>) > it is started dirtectly without a shell; that also makes > the journal easier to read. > > For all other cases; a one-line shell script is generated in /run. > Translating all possible shell escapes to systemd escapes > was too much pain/risk.
Ok cool. Thanks for explaining. Saludos
