https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #2 from Kevin Korb <rs...@sanitarium.net> --- I agree with Carson. If rsync is told to do the impossible it should fail with an appropriate error and exit code. Unfortunately I would also have to argue that the current behaviour is wrong because it does not exit with an error code and because I think the error message should also go to stderr instead of just syslog. A non-0 exit code would allow the launching script to simply keep trying until it works. I think even the systemd people would prefer an explicit failure over an exit 0 with no output. A program that fails to do what it was told to do shouldn't be effectively the same as /bin/true. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
