rsync - Nov 2007 - DO NOT REPLY [Bug 5079] New: rsync: failed to open "/path/to/file", continuing: Permission denied (13)

https://bugzilla.samba.org/show_bug.cgi?id=5079

           Summary: rsync: failed to open "/path/to/file", continuing:
                    Permission denied (13)
           Product: rsync
           Version: 3.0.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: peter.oliver@eon-uk.com
         QAContact: rsync-qa@samba.org


In the event that rsync encounters a file on the receiving end that it cannot
read, it will treat the file as if it is empty, try to replace it, and issue
the following message:

    rsync: failed to open "/path/to/file", continuing: Permission
denied (13)

However, even if it succeeds it will also issue this messages:

    rsync error: some files could not be transferred (code 23) at main.c(789)

This leads the user (and any scripts checking the return code) to believe that
the transfer has failed, when in fact it has succeeded.


-- 
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.

https://bugzilla.samba.org/show_bug.cgi?id=5079





------- Comment #1 from peter.oliver@eon-uk.com  2007-11-13 11:27 CST -------
Created an attachment (id=2966)
 --> (https://bugzilla.samba.org/attachment.cgi?id=2966&action=view)
s/FERROR/FINFO/

Turning this error message into a warning that does not set a return code
appears to be a simple matter of changing FERROR to FINFO for this 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.

https://bugzilla.samba.org/show_bug.cgi?id=5079


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #2 from wayned@samba.org  2007-11-22 12:34 CST -------
I have expanded the error codes that a protocol-30 rsync can send so that it
can indicate that a message is an error (which should go to stderr) without
causing the "some files could not be transferred" error at the end. 
So, this
is now fixed in the git repository.


-- 
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.