I try to sync netware.metadata extended attributes (described in http://developer.novell.com/documentation/xattr/attr_enu/data/bktitle.html) NSS store trustee information in structure zNW_trustee_s. It contains trustee ID and trustee rights(maximum 2043 trustees). rsync synchronise only new or changed trustees records. If i delete some trustee record from source, rsync doesn't delete it on target location. Also checked in rsync 3.0.5.
Copying of NetWare metadata per se is not currently a supported feature of rsync. Rsync simply copies the extended attributes exposed via the getxattr interface. If that does not have the effect of copying the NetWare metadata, that could be considered a flaw in the design of the netware.metadata xattr. Alternatively, if someone can identify what rsync could do specially in order to copy the NetWare metadata correctly, you could request it as an enhancement. From the documentation you linked, I get the impression that the data passed to setxattr(netware.metadata) is not literally the entire value to be set, but some form of request that indicates what parts of the xattr should be modified (arguably an abuse of the setxattr interface, but perhaps the most convenient approach). The zMOD_ALL_TRUSTEES flag sounds like it might be what is needed, but that's just a guess; its meaning is not documented.
The extended attributes it not function of products Novell. Novell uses standard interfaces for access granting to the features. I have resulted structure of the metadata for an example that doesn't synchronize rsync. For example, it is possible to tell on another: Before the first synchronization we have a set from 3 expanded attributes. Before the second synchronization we will remove 1 attribute from an initial file, and after synchronization we will receive on target again 3 expanded attributes. I consider that error to be in the logician of algorithm of synchronization xattr rsync. I will try to understand algorithm if I will receive result I will place it here.
(In reply to comment #2) > The extended attributes it not function of products Novell. Novell uses > standard interfaces for access granting to the features. I have resulted > structure of the metadata for an example that doesn't synchronize rsync. Sorry, I don't understand what you are saying here. > For > example, it is possible to tell on another: > Before the first synchronization we have a set from 3 expanded attributes. > Before the second synchronization we will remove 1 attribute from an initial > file, and after synchronization we will receive on target again 3 expanded > attributes. I consider that error to be in the logician of algorithm of > synchronization xattr rsync. There may be an rsync bug, or it may be that rsync is making the correct system calls but the NetWare implementation gives an unexpected result. We would need a system call trace (strace on Linux, I don't know the NetWare equivalent) to find out.
I use rsync on SUSE Linux Enterprise server with NSS file system(not on NetWare). If I start strace with rsync at synchronization it will help?
(In reply to comment #4) > If I start strace with rsync at synchronization it will help? Yes. Please do it for the simplest case you can find in which the outcome is incorrect and attach the output to this bug. If the run is remote, be sure to run strace on both sides (see http://rsync.samba.org/issues.html for how to do that).
Created attachment 6080 [details] First synchronization - 1 trustee are been processed
Created attachment 6081 [details] Second synchronization I delete 1 trustee from source. On target file trustee are not deleted.