Lapo Luchini wrote: > Lapo Luchini wrote: >> Dave Korn wrote: >>> It appears that cygwin has the xattr functions implemented and exported >> Of course I'd like to; I didn't hope it could be as easy as that. =) > > Yes, it seems it was as easy as that. > > % rsync-3.0.6-1/inst/usr/bin/rsync.exe --version > rsync version 3.0.6 protocol version 30 > Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. > Web site: http://rsync.samba.org/ > Capabilities: > 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, > socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, > append, ACLs, xattrs, iconv, symtimes > > "make check" tests seems to have good results too, except the xattr one > is a SKIP. > Mhhh, that depends on a missing commandline "setfattr" utility. > But the package itself could be GTG anyways (it sure shouldn't be > "worse" than the current 3.0.5 one). > ---- On my linux box there's an 'xattr' command to set attribs on xfs files systems and is compatible with the Irix command of the same name.
But if rsync makes the extended attr calls internally, the xattr call shouldn't be explicitly needed. Samba has to be set to pass through the xattr calls to the underlying file system on each share "ea support = yes". According to the docs it will enable storing of what it calls "OS/2" style extended attribs by using the native file systems extended attribute system. So 'ideally', *cough*, it should just work. I can always check to see if extended attr's show up on my linux file system. Was writing a script to run xattr over my files -- it's a primitive util that doesn't support wildcards or recursion. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
