rsync - Aug 2017 - [Bug 12955] New: [patch] Fix rsync -A on AIX

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

            Bug ID: 12955
           Summary: [patch] Fix rsync -A on AIX
           Product: rsync
           Version: 3.1.2
          Hardware: PPC
                OS: AIX
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: gongcunjust at gmail.com
        QA Contact: rsync-qa at samba.org

Created attachment 13458
  --> https://bugzilla.samba.org/attachment.cgi?id=13458&action=edit
Fix rsync -A on AIX

Hello,

When use rsync (version 3.1.2) to synchronize ACLs files (rsync -A) on
AIX 7.2(also on AIX 6.1 and AIX 5.3), the errors would occur as
follows:

  rsync: change_sacl_perms: sys_acl_get_tag_type(): No such file or directory
(2)

or

  rsync: change_sacl_perms: sys_acl_get_tag_type(): Error 0 (0)

This patch fixes the problem and has been tested on AIX 5.3, 6.1 and 7.2.

It also has been tested to synchronize ACLs files from Linux to AIX.

Thanks.

Cun

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

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

Cun Gong <gongcunjust at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #13458|0                           |1
        is obsolete|                            |
                 CC|                            |gongcunjust at gmail.com

--- Comment #1 from Cun Gong <gongcunjust at gmail.com> ---
Created attachment 13478
  --> https://bugzilla.samba.org/attachment.cgi?id=13478&action=edit
Fix rsync ACL files on AIX

Because the chmod(2) will disable ACL permission on AIX (see
https://www.ibm.com/support/knowledgecenter/en/ssw_aix_72/com.ibm.aix.security/access_control_list.htm),
so this is a full patch for fixing the problem that can't synchronize ACL
files
on AIX.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.