similar to: Is there any easy way to set some default rsync options?

On Wed 16 Oct 2024, Chris Green via rsync wrote: > > I use it almost exclusively on Linux systems and it would be really > handy if I could set a number of options which would always be used > when I run rsync. These would be in addition to -a which is useful > but not quite enough. > > In particular I always want to copy extended attributes (-X), ACLs > (-A) and

We've been using RSYNC to back things up and it's sick nasty wicked awesome. Recently we migrated our receiving server to a different machine (Debian lenny) and now we're running into this DROP-CACHE: UNKNOWN OPTION error: sender-machine$ *rsync -Cvaz -e ssh --delete --exclude blah/ --exclude yadda/ . user at receiver:/path/for/drop* rsync: on remote machine: --drop-cache: unknown

While installing rsync on a new Sun Netra running Solaris 2.8, two tests (chgrp and hardlinks) failed. I found that these tests execute rsync while other successfull tests exectute $RSYNC. It is fortunate that my shell path was quite restricted and that no earlier version of rsync was installed on my path. The system would have run the chgrp and hardlinks tests with an earlier rsync if it had

Hi, I noticed a weird problem with "make test" on rsync-2.5.5. It seems that the testsuite only works if rsync is already installed (presumably an older version...). I think the tests intend to run the rsync that was just built and not the previously existing rsync, but is not what appears to happen. The test script output contains messages like this: Running: "rsync -aHvv

Is there any performance problem with hard links in ZFS? I have a large storage. There will be near 50000 hard links for every file. Is it ok for ZFS? May be some problems with snapshots(every 30 minutes there will be a snapshot creating)? What about difference in speed while working with 50000 hardlinks or 50000 different files? ps: It would be very useful if you give me some links about

When I compile on Solaris * I get the foillowing errors: bash-2.03# gmake gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c rsync.c -o rsync.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c generator.c -o generator.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c receiver.c -o receiver.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c cleanup.c -o cleanup.o gcc

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,

There is the problem which I discribed here https://bugs.centos.org/view.php?id=12820. rsync does not break hard-link into destination if hard-link has be broken in source with option inplace. The problem remains in the latest version of rsync? -- View this message in context: http://samba.2283325.n4.nabble.com/There-is-problem-of-rsync-with-options-hard-links-inplace-tp4714872.html Sent from

Hi, i use rsync version 2.6.9 protocol version 29 on Mac OS X 10.6.3 and expierienced the following problem. When using --link-dest=DIR with DIR on the startup volume everything works fine. If DIR is a volume on an external drive many files are copied instead of creating hard links. hardlinks are create e.g. fom .jpg files and from .rtf files but not from .doc files and many other files. The

On Tuesday 13 August 2013 12:23 PM, Joe wrote: > Is there any way at all to say which is the original file and which is > the hard link? I'll bet there isn't, although I' m not an internals guy > at all. If so, this would be impossible to do. The inode is the > "original", but all the file table entries to it are hard links (if > they're not symlinks.) >

I have been trying for quite a while now to understand why is the flist.c:f_name() function implemented using static buffers. Anyone care to comment? The immediate problem is that any call to f_name overrides the previous content (well, obvious). This, combined with the fact that several function calls are made with the result of f_name(file) results in problems handling hardlinks - and

https://bugzilla.samba.org/show_bug.cgi?id=6276 Summary: crtimes.patch does not preserve creation dates on Mac x86_64 only Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Please CC me directly as i'm not on the list. I have attached a patch against latest CVS (cvs diff -u) that adds the following functionality. I can break it up if you would prefer it in pieces. Comments welcome. o add compare-perms option This creates a new inode for a file even if only the perms have changed. This way if a file outside of destdir is hardlinked to a dentry inside

Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -------------------------------------------------------------- #! /bin/sh # # set -x DIR="/var/tmp/rsync_$(date +%s)/" mkdir "${DIR}/" # Preparing dir_A mkdir

Hello, I have a weird issue with rsync randomly marking some files as having a different checksum (see sample outputs below - run one after another). You would think it is some kind of corruption / io problem with the files but it doesn't seem so - I have copied files around, changes source to different machines, counted md5s manually 100s of times - always the same. All files except

I've gone through the CVS commit log and tried to get every user-visible change since 2.4.6, so that we can make a proper announcement for 2.4.7. Please let me know if anything is missing/inaccurate. At this stage I'm planning to release two 2.4.7pre tarballs, one with the "large nohang patch" and one without. Some people inside VA will be stress-testing both, and so we can

Hi All, Any inputs on this issue? -- Shedi On Wed, Feb 21, 2024 at 5:12?PM Shreenidhi Shedi < shreenidhi.shedi at broadcom.com> wrote: > Hi All, > > Copying the content from the GH issue as is. > Need your inputs on the same. > FWIW, the coredump files generated in linux have xattr values which are > > 32 bytes. > > https://github.com/WayneD/rsync/issues/569

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

https://bugzilla.samba.org/show_bug.cgi?id=5022 Summary: FreeBSD 4.11 - Compilation Fails - uidlist.c - gcc2 / gcc3 Product: rsync Version: 3.0.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, Our organization hosts a specialized Linux distribution. As is typical with Linux distributions, the set of files that make up our Linux distro contains a very complex web of self-referential hard links. Several other sites use our Linux distro and maintain either partial or full internal mirror copies of it. The standard method used by Linux mirror sites to pull/replicate a subset of a