On Tue, 8 Oct 2019, Simon Levermann wrote:
Okt 08 18:45:27 slevermann.de systemd[1]: tarsnap-backup.service: Main process exited, code=exited, status=1/FAILURE Okt 08 18:45:27 slevermann.de systemd[1]: tarsnap-backup.service: Failed with result 'exit-code'.
systemd tracks everything - system calls, signals, exit codes during execution of a service. Fortunately, it still things SIGPIPE is "okay". systemd also tries to guess what is the "main" process of the service, it tracks (among others) forks and may believe /usr/bin/tarsnap binary is the "main" and the most important process indeed and track its exit code instead. https://lists.debian.org/debian-user/2016/10/msg00422.html Can you try setting GuessMainPID=no in the [Service] section of the unit file? Marcin
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature