rsync - Jul 2006 - DO NOT REPLY [Bug 3978] New: readonly source -> incomplete transfers (permission problems)

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

           Summary: readonly source -> incomplete transfers (permission
                    problems)
           Product: rsync
           Version: 2.6.4
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: r.e.wolff@bitwizard.nl
         QAContact: rsync-qa@samba.org


When transferring large datasets where the destination is not consistent anyway
until the transfer is complete I use --inplace.

Part of using rsync is that I can interrupt the transfer and restart it without
wasting bandwidth. 

interrupting rsync causes the file to be left in "mode 0" state.
(indicates
it's not complete, I can understand this.)

restarting rsync causes rsync to fail opening the file, then it seems to ignore
the returned error code, next it transfers the whole file, and looses the
result.


Suggestion: As the file is mode 0 during the original transfer anyway, the mode
of the destination file should not be considered "holy". If the open
fails,
attempt to chmod the file to mode 600 and retry. 

This is "wrong" if the destination user explicitly chmods the
destination to
owner-read-only to prevent rsync from messing with them. 

How about leaving the incomplete file mode "200" instead of
"000"?

Or drop the "--inplace" for this file (which would have made it a full
no-op in
my case).

I apologise for reporting this on such an old version, but I'm not set up to
compile rsync on a whim.


-- 
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=3978


wayned@samba.org changed:

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




------- Comment #1 from wayned@samba.org  2006-09-17 19:50 MST -------
This was fixed in CVS back on July 30th:  a newly created file is now created
with owner read/write permissions, which allows an interrupted transfer to
continue to update the new file.


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