rsync - Nov 2010 - DO NOT REPLY [Bug 7783] New: add no-executability option

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

           Summary: add no-executability option
           Product: rsync
           Version: 3.0.7
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: uhlar at fantomas.sk
         QAContact: rsync-qa at samba.org


Please add option for rsync that will skip all executability checks and will
not set files executable, no matter whether existing or newly created. 

There are cases where source files are executable, but the destination files
don't need/have to be and using the umask is just enough.


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


wayned at samba.org changed:

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




------- Comment #1 from wayned at samba.org  2010-11-08 21:50 CST -------
See --chmod=a-x.


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





------- Comment #2 from uhlar at fantomas.sk  2010-11-09 01:53 CST -------
The point was to avoid calling chmod() at all, and add no--executability as
there is executability without its opposite.

But I see strace showing that chmod() is always called so we won't spare
system
calls here


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