similar to: [PATCH] Add --omit-{device,special}-times options

Hi all, I recently ran into some problems with rsync. My plan is to renew some of our old administration concepts from early 90's, I already replaced rdist with rsync a few years ago. Because of the rdist legacy, the current method requires synchronizing files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep}, which in turn are prioritized by a tool that just symlinks

Device files should be counted as devices, not symlinks. Marc. diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/delete.c devel-3.2.7/delete.c --- rsync-3.2.7/delete.c 2020-06-13 20:15:02.000000000 -0600 +++ devel-3.2.7/delete.c 2020-06-13 20:15:02.000000000 -0600 @@ -188,7 +188,7 @@ enum delret delete_item(char *fbuf, uint16 mode, uint16 flags) stats.deleted_symlinks++; #endif else if

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

When syncing from Linux to Aix --itemize-changes with --perms lists directories every time because the high-order st_mode bits for directories differ between the two systems, and itemize() isn't masking them with CHMOD_BITS. Here is a fix, tested with 2.6.6pre1. PS: I'm not subscribed to this mailing list, please Cc: if you need more info from me. Thanks. --- generator.c.~1~ Thu Jun

s/receiveing/receiving/ Marc. diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/rsync.1.md devel-3.2.7/rsync.1.md --- rsync-3.2.7/rsync.1.md 2022-10-16 13:27:30.000000000 -0600 +++ devel-3.2.7/rsync.1.md 2022-10-16 13:27:30.000000000 -0600 @@ -245,7 +245,7 @@ to be copied to different destination directories using more than one copy. While a copy of a case-ignoring filesystem to a case-ignoring

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

Commit-ID: dc3d109d1cac129e5b6d055eab5a8a277fdd06c5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=dc3d109d1cac129e5b6d055eab5a8a277fdd06c5 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 30 Oct 2014 11:53:35 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [PARSER] Catch

Commit-ID: da8fe1346c93b339333207adecd8493ca1cb403a Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=da8fe1346c93b339333207adecd8493ca1cb403a Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 30 Oct 2014 11:53:35 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [PARSER] Catch

https://bugzilla.samba.org/show_bug.cgi?id=4907 Summary: --disable-ipv6 disables -4 option Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: safari-samba-bugzilla-

--- When a bunch of --no-* options were added (852e763b), --no-y was forgotten. Here it is. Matt options.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/options.c b/options.c index 4ac8846..82597bf 100644 --- a/options.c +++ b/options.c @@ -577,6 +577,7 @@ static struct poptOption long_options[] = { {"link-dest", 0, POPT_ARG_STRING, 0,

Hi! As I commonly spell --inplace as --in-place, I'd like to suggest this simple patch: commit 5689f99b702788044a45e13582559832cf986328 Author: Jan-Benedict Glaw <jbglaw at lug-owl.de> Date: Wed Jun 26 22:49:31 2019 +0200 Allow "--in-place" as an alternative option name for "--inplace". diff --git a/options.c b/options.c index e5b0cb68..7ff0c51d 100644 ---

We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (sun/linux/netapp). This shows the problem: [Note my home directory is NFS mounted]

In some filesystems, typically optimized for large I/O throughputs (like IBM GPFS, IBM SAN FS, or distributed filesystems in general) a lot of lseek() operations can strongly impact on performances. In this cases it can be helpful to enlarge the block size used to handle sparse files directly from a command line parameter. For example, using a sparse write size of 32KB, I've been able to

This is the second generation of the edit-livecd tool that replaces our original bash script with a python version and aims to reuse as much as the livecd-creator libraries as possible. The main reason for the new creator class is to avoid the need for a kisckstart file in order to edit an existing livecd image. edit-livecd is useful for people who don't have the development and yum

double-colon mode doesn't work in CVS version. -vv says port number is 0. % rsync -vv host.domain::any opening tcp connection to host.domain port 0 rsync: failed to connect to host.domain: Can't assign requested address (49) rsync error: error in socket IO (code 10) at clientserver.c(94) And --port=873 cannot be used in client mode now. I made a small sample patch. (Sorry, I

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

This patch adds a switch --fat-filenames which replaces all characters that aren't legal on FAT filesystems with an underscore. This is the first time I touch the rsync code, so I may not be going about it the right way, but it seems to be working. Naturally there's some potential for collisions, but it's probably better than what happens currently (such files are simply not copied).

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> zstd compression was announced as "good compression with high throughput" so I gave it a try. With zlib, on high speed links the CPU is usually the bottle neck. With zstd I'm able to fill a 200Mbit link :) zstd detection happens automatically via pkg-config. No zstd header means no error about missing zstd. So that

Any feedback on this patch and the possibility of getting it into CVS or the patches directory? Thanks, Craig ---------- Forwarded message ---------- To: jw schultz <jw@pegasys.ws> From: Craig Barratt <cbarratt@users.sourceforge.net> cc: rsync@lists.samba.org Date: Sat, 01 May 2004 17:06:10 -0700 Subject: Re: setting checksum_seed jw schultz writes: > > > There was some

We needed the group id bit to always be set on directories when rsync creates them. We always run rsync from a script with just the -ltR options. The destination file system uses acl's to control file access so new files need to inherit the properties of the directories they're in. (This is for IBM's global storage architecture on Aix or Linux). I made the following changes to make