[Bug 8967] rsync returns with non-zero exit code when killed by SIGTERM

samba-bugs at samba.org samba-bugs at samba.org
Fri Jun 1 12:00:13 MDT 2012


--- Comment #2 from mus.svz at gmail.com 2012-06-01 18:00:13 UTC ---
that's not the point. This is something that must be fixed in rsync, not in
systemd. systemd does the right thing: if the process exits with 0, everything
is ok, if not, something went wrong. "making systemd more flexible" in this
regard would just be a pointless workaround.
Why should killing a process with SIGTERM be considered an error? This doesn't
make sense and I don't now about any other daemon that does this.

Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the rsync mailing list