search for: smb_acl_type_default

...sync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.0cvs] If I try with rsync 2.6.9 with ACL patch, I get this instead: building file list ... done ./ rsync: set_acl: sys_acl_set_file(., SMB_ACL_TYPE_ACCESS): Invalid argument (22) rsync: set_acl: sys_acl_set_file(., SMB_ACL_TYPE_DEFAULT): Invalid argument (22) dossier1/ rsync: set_acl: sys_acl_set_file(dossier1, SMB_ACL_TYPE_ACCESS): Invalid argument (22) rsync: set_acl: sys_acl_set_file(dossier1, SMB_ACL_TYPE_DEFAULT): Invalid argument (22) rsync: set_acl: sys_acl_set_file(dossier1/essai1.doc, SMB_ACL_TYPE_ACCESS): Invalid argume...

...(in test) failed: Permission denied (13) 2006/09/21 04:34:58 [6860] rsync: stat "/linux/documentation/perl/perl_networking/ch17" (in test) failed: Permission denied (13) 2006/09/21 04:34:58 [6860] default_perms_for_dir: sys_acl_get_file(linux/documentation/perl/perl_networking/ch17, SMB_ACL_TYPE_DEFAULT): Permission denied, falling back on umask Tried this with and without use chroot = true but it made no difference. Tried changing the order of the chmod directives to incoming chmod = Fug=rw,Fo-rwx,Dg=s,Dug=rwx,Do-rwx but it also made no difference. Am I misunderstanding the chmod stu...

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

...ReportedBy: hashproduct@verizon.net QAContact: rsync-qa@samba.org Run the following in an empty directory: mkdir a touch a/b rsync --relative --no-implied-dirs a/b dest/ The following error messages result (my indentation): default_perms_for_dir: sys_acl_get_file(a, SMB_ACL_TYPE_DEFAULT): No such file or directory, falling back on umask default_perms_for_dir: sys_acl_get_file(a, SMB_ACL_TYPE_DEFAULT): No such file or directory, falling back on umask rsync error: some files could not be transferred (code 23) at main.c(882) [sender] The trouble is th...

In the mandriva rpm of rsync, we apply for our rpm the acl patch in the patches directory. I am trying to update our rpm to rsync 2.6.6 but one of the test failed with this patch. It seems to be a minor problem, but can you have a look ? Thanks by advance. Following the message (a bit long): ----- itemize log follows Testing for symlinks using 'test -h' +

...ollowing bug report on the Debian rsync which has the ACL patch applied: On Fri 01 Dec 2006, Bryan Gartner wrote: > > When using the rltvz options to mirror files from a remote server, these > kinds of issues are reported: > > default_perms_for_dir: sys_acl_get_file(wallpaper, SMB_ACL_TYPE_DEFAULT): > Function not implemented, falling back on umask > > This is true for both 2.6.9-1 and 2.6.9-2 versions on this (hppa) platform, > but doesn't seem to exist on i386 versions. > > A workaround is simply to use "avz" cmd-line options, but this issue is > ne...

hello, I am getting the following with rsync 2.6.9: > :~/tmp/rsync> mkdir a > :~/tmp/rsync> mkdir a/dir > :~/tmp/rsync> touch a/dir/file > :~/tmp/rsync> mkdir b > :~/tmp/rsync> rsync -r --existing a/ b > default_perms_for_dir: sys_acl_get_file(dir, SMB_ACL_TYPE_DEFAULT): No such file or directory, falling back on umask > rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9] Is it a bug? Thanks a lot, Misha

...t: rsync-qa@samba.org I am getting the following with rsync 2.6.9: > :~/tmp/rsync> mkdir a > :~/tmp/rsync> mkdir a/dir > :~/tmp/rsync> touch a/dir/file > :~/tmp/rsync> mkdir b > :~/tmp/rsync> rsync -r --existing a/ b > default_perms_for_dir: sys_acl_get_file(dir, SMB_ACL_TYPE_DEFAULT): No such file or directory, falling back on umask > rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9] -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact fo...