similar to: Rsync 3.0.0pre4 errors with ACLs and Xattrs between OSX and Linux

Hello, I found that using rsync on OS X can give some problems when it comes to Extended Attributes (-X flag). The server I use has Ubuntu with the filesystem XFS and I am trying to backup a OS X system to it. The problem is as far as I understand it that Linux Kernel has a liming on 64k f?r Extended Attributes and OS X don?t have this limit. Some error output. rsync: rsync_xal_set:

https://bugzilla.samba.org/show_bug.cgi?id=14377 Bug ID: 14377 Summary: rsync rsync_xal_set lsetxattr failed invalid argument Product: rsync Version: 3.1.3 Hardware: All OS: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne at opencoder.net

I am using the latest 3.0.0cvs protocol version 30 Capabilities: 64- bit files, 32-bit system inums, 64-bit internal inums, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, no ACLs, xattrs xattrs cvs 1.77 I installed xattr for Mac OSX Senario: $ mkdir /Users/alan/Desktop/folder1 $ echo 'Hello' > /Users/alan/Desktop/folder1/file1 $ xattr --set color blue

Hi Kevin, Thanks for your quick response. The rsyncd.conf file looks like: charset = utf-8 [user] path = /c/user comment = "" use chroot = true uid = root gid = root read only = false auth users = admin I'm still confused about how to specify the path. The actual UNIX path is: /c/user/snapshots/rsync_test/last I've tried: --link-dest=snapshots/rsync_test/last

https://bugzilla.samba.org/show_bug.cgi?id=8456 Summary: improve --link-dest bahaviour Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: toralf.foerster at gmx.de

https://bugzilla.samba.org/show_bug.cgi?id=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr

machine O is outside firewall, machine I is inside (machine names changed to protect the innocent :-) firewall allows ssh connections if inititiated from I to O, but not if the other way. both machines have an /etc/rsyncd.conf of: [rt] path = /tmp/rsync_test comment = Test area O runs rsync daemon, I initiates a rsync cammnad like rsync -rvvv --delete --rsh=ssh O::rt /tmp/rsync_test

Hi all, I'm trying to figure out why a script works when using SSH but not when using the rsync protocol. When I run the following command: rsync -aPh --link-dest=/user/snapshots/rsync_test/last /home/user/rsync_test root at readynas.internal:/user/snapshots/rsync_test/Jan_11_2025 it works perfectly, correctly recognizing the link-dest parameter. However, when I try to run the same command

rsyncd doesn't take unix paths. You must adapt your --link-dest to contend with however the rsycd module is defined in rsyncd.conf. On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote: > Hi all, > > I'm trying to figure out why a script works when using SSH but not > when using the rsync protocol. When I run the following command: > > rsync -aPh

On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote: > Thanks for your quick response. The rsyncd.conf file looks like: > > charset = utf-8 > [user] > path = /c/user > comment = "" > use chroot = true Note the chroot... So "/" equals /c/user > uid = root > gid = root > read only = false > auth users = admin > > I'm

I am attempting to rsync data from a rsync server and set the permissions to a different gid on the client: my servers name is "rserver01" my clients name is "rclient01" here is the rysync.conf contained on rserver01: # log file log file = /var/adm/rsync_log # global options for all modules dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz uid = nobody

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

I think your product is awesome, but I am experiencing an unexpected behaviour. $ rsync -avviPH /Users/alan/Desktop/rsync_test\ Folder/ root@slug::Downloads opening tcp connection to slug port 873 sending daemon args: --server -vvlHogDtpre30.16i "--log-format=%i" -- partial . Downloads sending incremental file list .d..t..g... ./ rsync: failed to write xattr user.rsync.%stat for

Hi HAT! Nice to meet you over here... ;) On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote: > Hi. > I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. > I confirmed that ResourceFork and FinderInfo are compatible with > Netatalk 3.1.7. However, EAs are incompatible. > The character ":" in EA name is wrong. > The EAs are not seen from clients. >

In case of FreeBSD, the name of the extended attribute is wrong. % lsextattr user ICONandEA.txt ICONandEA.txt netatalk.Metadata com.apple.TextEncoding com.apple.metadata:kMDItemFinderComment "netatalk.Metadata" is incompatible to Netatalk. The first atom "org." is removed. source3/include/smb.h: /* Prefix for DosStreams in the vfs_streams_xattr module */ #define

Rsync maintainers please review rsync bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98740 The code in question is in socket.c in start_accept_loop. The user is getting these warning messages:

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving

I'm trying to understand how to properly setup the /etc/rsyncd.conf file to run an rsync daemon with a secrets file specified in a module - the rsync.conf manpage does not spell it out clearly enough. Rsync server is rsync-2.5.6. If this is my /etc/rsyncd.conf file: ------------------------------------ log file = /var/log/rsync uid = root gid = root [test] uid = rsync1 gid =

Hi, I detected a silly behaviour of rsync when new hardlinks of already synced files are created: Scenario: There are a local directory and a equal remote directory created by former run of rsync. Create a hardlink from a already existing file (both inside the local directory). If this hardlink has a filename with comes before the original filename when both are sorted in alphabetic order,

I see that rsync will eventually support extended attributes, which will be great. But: will it allow backup from a file system that supports xattrs, to one that does not? For this to work, rsync would have to represent the xattrs on the destination machine in some special format, I suppose, which is outside the usual rsync mode of operation. Moreover, even if both machines support