similar to: doc & examples bug regarding 'xattr' special switch need

Does rsync support acl and xattr (as with acl and user_xattr mount options)? I saw some acl patches for rsync, so probably it's not officially blessed yet. However, I didn't see any xattr patches - although some talks about it on the list go back into year 2003. So how it is with support for these? If I backup a Samba server, which has a filesystem mounted with acl,user_xattr (with

Linda Walsh <flac at tlinx.org> wrote: ... > That brings up another question then... What is 'hi' (v. low?)... Zero, or close to zero, is low. 12 is high. ... > What's a subset stream? This is explained at: http://flac.sourceforge.net/format.html in the bulleted point beginning, "FLAC specifies a subset of itself as the Subset format." ... > Another

Hi I'd like to know if OCFS2 1.4 on RHEL5 with the REDHAT latest kernel supports disk quotas, the xattr and acl. I could have done something wrong but only the acl seem to work. Apparently instead on FC12, where support is enabled in the kernel itself OCFS grep / boot / config * CONFIG_OCFS2_FS = m CONFIG_OCFS2_FS_O2CB = m CONFIG_OCFS2_FS_USERSPACE_CLUSTER = m # CONFIG_OCFS2_FS_STATS is

Emmanuel Florac via samba wrote: > Unknown parameter encountered: "winbind enumerate users" > Ignoring unknown parameter "winbind enumerate users" > Unknown parameter encountered: "winbind enumerate groups" > Ignoring unknown parameter "winbind enumerate groups" It may be irrelevant, but I have: winbind enum groups = Yes winbind enum users

Emmanuel Florac wrote: > id TESTAD\\testuser > returns "no such user" and > > getent passwd TESTAD\\testuser > > returns a "2" code. > ---- On linux, to get 'domain\user' to resolve, I had to have those entries in my /etc/passwd (and /etc/group for groups). I.e. *w/o krb*, (in samba 3.x), I had entries like:

Familiar? protocol error on a local file copy? How can I have a proto incompat when it it is talking to itself?... This was on the ERROUT... rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) File-list index 531530 not in 531937 - 533437 (finish_hard_link) [generator] rsync error: protocol incompatibility (code 2) at rsync.c(652) [generator=3.0.9] rsync:

Documentation/ext3.txt suggests that the "user_xattr" and "acl" mount options are on by default. This doesn't seem to be the case, as the kernel deduces the default mount options from the filesystem superblock, and mke2fs does not appear to write any default mount options there. This error was spotted by Jacques de Mer. Signed-off-by: Daniel Drake <dsd at

Hi We are building a Linux app under Centos 5.3, using gnu make 3.81 and gcc 4.12. The working directory is on a remote machine and is either a Samba share or a Windows 7 share. We find that in the case of a Windows 7 share the resulting executable has the sticky bit set in group: On Windows 7 share: -rwxrwSrwx 1 <snip> myapp On Samba share: -rwxrwx--x+ 1 <snip> myapp The

Hello everyone, Got a weird ACL issue: First of all, my Linux host is fully ACL enabled (kernel support, file system support, mount with xattr, library support, samba compilation support, all set). Then a share is created with vfs acl_xattr and ea support on, got mounted on a Windows client as administrator, and a directory created right under the drive. The issue is when I was checking out the

Was there some reason that patch got dropped? Otherwise rsync eats up all the buffer memory. Note -- I tried directio -- didn't work due to alignment issues -- buffers have to be aligned to sectors. The kernel, if I remember correctly, has been on again/off again on requiring alignment on directio -- because most of the drivers and devices do for directio to work, at. "dd"

I realized in looking at my smb.conf, I'm not using these in a consistent manner, and .... well I just don't understand what the differences are between them. Sure I can read the smb.conf page: %U session username (the username that the client wanted, not necessarily the same as the one they got). vs. %u username of the current service, if any. ---

https://bugzilla.samba.org/show_bug.cgi?id=10496 Summary: --itemize-changes always reports xattr changes with --xattrs --fake-super Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

I'm trying to find out what's causing this slowdown -- it's INTOLERABLE.... over 1 minute and less than 1% done. (400MB file)... After trying 3 times, I gave up and logged in using X to the server and ran Tbird from there.... Mail sent out in < 1 minute, though the copy to dovecot took about 50% longer. So... I looked at the network trace. and everyfrackin' body was

Yves Goergen wrote: > The issue still exists. Can anybody explain to me why dovecot creates > IMAP folders with the wrong filesystem permissions? On a lark, I looked through my dirs @ permissions. Shorted lines a bit so they'd fit w/o extra lines between them using: (get rid of text before permissions, and shorten user/group to a few letter) find . -type d -ls|sed -r

https://bugzilla.samba.org/show_bug.cgi?id=10322 Summary: Slow Performance over Network rsync Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: Joerg.Grube at Gmx.De

Maybe rsync could support extattrs on non-supporting fs's with a .<fn>.xattr file stored at the same place as the <fn>: If a user used a switch to emulate 'xattrs', then on a fs that didn't support real .xattrs one could still ACL and other .xattr info. If a user ran rsync w/o that switch such files would be treated as 'normal files' -- allowing copying

Why would the samba list be looking for a reverse host name via IPV6? IFAIK I only have an IPv4 addr and reverse addr. I don't know if the original went to the person in france or not. Anyone else getting bounces like this? -------- Original Message -------- Subject: Returned mail: see transcript for details Date: Tue, 7 Apr 2015 13:19:19 -0700 From: Mail Delivery Subsystem

In the smb.conf manpage, there is a notation used, (G) or (S) for global or share. Does (S) mean it can only be used in a Share section (i.e. - will be ignored in the global section), or is that they *can* be applied at the share level, and, possibly set a default in the 'G'lobal section? example: "ea support = yes" Seems like that could mean that extended attrs are

Hi, I am trying samba4 alpha5 because I would like to use the feature of xattr for ACL. I followed the howto.txt comes with it exactly. I found that if I use user_xattr in /etc/fstab, I got "System cannot find the file specified" error very often (more than 50% of the time) when I try to create a file from a windows machine using share test (dir /data/test on samba server). If I

First things first. Thanks to all samba developers and this great community. Some background info: I have a Samba 4.1.9 AD domain controller alone at the moment running on FreeBSD 9.2 with aprox. 50 clients, and a TS. The clients are mixed, mostly 7 and XP SP2. Due to a hard drive failure I ended up with a messed up db and a lot of problems, almost all of them including frequent panics in the