samba-bugs@samba.org
2007-Oct-14 21:23 UTC
DO NOT REPLY [Bug 4611] i always get "rsync error: some files could not be transferred (code 23)" even when there is nothing to transfer
https://bugzilla.samba.org/show_bug.cgi?id=4611 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Summary|i always get "rsync error: |i always get "rsync error: |some files could not be |some files could not be |transferred (code 23)" even |transferred (code 23)" even |when there is nothing to |when there is nothing to |transfer |transfer Version|2.6.9 |3.0.0 ------- Comment #1 from wayned@samba.org 2007-10-14 16:23 CST ------- The reason for the error-exit value is that rsync output that message about not using the RSYNC_PASSWORD environment variable as an error, which makes rsync think that something went wrong with the file transfer. I could have changed the message from an "FERROR" to an "FINFO" message, but I don't see the purpose in having rsync comment on the presence of an environment variable when it was explicitly told to use a file on the command-line. I have fixed in this in CVS by removing the message. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
Seemingly Similar Threads
- Redirect --stats to STDERR.
- [Bug 1764] New: dry-run does not show changes in owner / group, permission, or timestamp
- 2.6.0 "file has vanished" fails to set exit code on local client
- DO NOT REPLY [Bug 4899] New: When a mounted dir cannot be visited, rsync will halt there and the shell is halted, even "ctrl -c" can't quit it.
- [PATCH] --source-filter && --dest-filter for rsync 2.5.6