samba-bugs at samba.org
2013-Jul-16 12:51 UTC
[Bug 10024] New: rsync cannot delete remote file, yet exit value is 0.
https://bugzilla.samba.org/show_bug.cgi?id=10024 Summary: rsync cannot delete remote file, yet exit value is 0. Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: samba-bugzilla-contributor at famsik.de QAContact: rsync-qa at samba.org Created attachment 9052 --> https://bugzilla.samba.org/attachment.cgi?id=9052 Shell script that shows the problem. Done: Some recursive rsync that should have deleted a remote subdirectory with some files in it. It cannot do that, as the permissions on the remote machine don't allow deletion. Expected: rsync should give a useful error message and terminate with an exit value that is not 0. Seen: While rsync does give a useful error message, it terminates with exit value 0. I enclose a script that demonstrates the problem, with rsync version 3.0.9 on both ends. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2013-Jul-19 16:00 UTC
[Bug 10024] rsync cannot delete remote file, yet exit value is 0.
https://bugzilla.samba.org/show_bug.cgi?id=10024 --- Comment #1 from Wayne Davison <wayned at samba.org> 2013-07-19 16:00:05 UTC --- Please test 3.1.0dev instead. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2013-Jul-19 21:01 UTC
[Bug 10024] rsync cannot delete remote file, yet exit value is 0.
https://bugzilla.samba.org/show_bug.cgi?id=10024 Andreas Kr?ger <samba-bugzilla-contributor at famsik.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|3.0.9 |3.1.0 --- Comment #2 from Andreas Kr?ger <samba-bugzilla-contributor at famsik.de> 2013-07-19 21:01:15 UTC --- I grabbed the git sources as of 2013-07-13 and buildm62327b1281be9151423048235573e0ca208fc095 on my machine. Used that compile results on both ends, by using localhost and adding --rsync-path in my script as provided. The bug reproduces with that version. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2013-Dec-23 18:33 UTC
[Bug 10024] rsync cannot delete remote file, yet exit value is 0.
https://bugzilla.samba.org/show_bug.cgi?id=10024 Wayne Davison <wayned at samba.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Wayne Davison <wayned at samba.org> 2013-12-23 18:33:14 UTC --- I checked in a fix for this the other day. Thanks for the report! -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2014-May-15 14:16 UTC
[Bug 10024] rsync cannot delete remote file, yet exit value is 0.
https://bugzilla.samba.org/show_bug.cgi?id=10024 Peter <peto2468 at hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peto2468 at hotmail.com --- Comment #4 from Peter <peto2468 at hotmail.com> 2014-05-15 14:16:50 UTC --- The same problem persists for flags --remove-source-files, no error value is returned when remote files could not be deleted, eg. due to no write permissions. Tested on 3.1.1pre version. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Apparently Analagous Threads
- [Bug 931] Allow ssh-connections through a HTTP proxy (such as squid).
- DO NOT REPLY [Bug 7124] New: Error exit causes I/O error
- [Bug 8967] New: rsync returns with non-zero exit code when killed by SIGTERM
- [Bug 9882] New: Incorrect exit code when sender over SSH is killed with SIGTERM
- Dummy (factor) based on a pair of variables