similar to: [patch] Replace illegal characters in filenames for FAT (switch)

diff --git a/clientserver.c b/clientserver.c index 2d7c28f..694a72d 100644 --- a/clientserver.c +++ b/clientserver.c @@ -806,6 +806,7 @@ static int rsync_module(int f_in, int f_out, int i, char *addr, char *host) exit_cleanup(RERR_UNSUPPORTED); } +#ifdef ICONV_OPTION if (!iconv_opt) { if (ic_send != (iconv_t)-1) { iconv_close(ic_send); @@ -816,6 +817,7 @@ static int

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

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

https://bugzilla.samba.org/show_bug.cgi?id=7565 Summary: --check-point=<TIME> +options.c.patch +generator.c.patch Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com

I am backing up files from Linux to a NTFS using rsync. I have the NTFS mounted on Linux via CIFS. I am discovering errors while attempting to backup files with restricted NTFS characters, like : [colon]. For example, I am unable to backup my crucial maildirs, as a colon is encoded in each Linux file path. Is there a solution to rsync Linux file paths with restricted NTFS characters, to NTFS?

Similar to --omit-{dir,link}-times: --omit-device-times omit device files from --times --omit-special-times omit sockets and fifos from --times Also, fix corner case that allows --omit-dir-times to be ignored. See unchanged_attrs() and recv_generator()'s call to try_dests_non(). Marc. diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/generator.c devel-3.2.7/generator.c ---

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 ---

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

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

https://bugzilla.samba.org/show_bug.cgi?id=5012 Summary: iconv: client charset used by server process Product: rsync Version: 3.0.0 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: kaarle@web.de

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 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

Went to use ActiveSupport in a gem today and got an error on account of not having i18n installed. Either bundler should be installing i18n along with activesupport or docs need to be updated. quick repro: https://github.com/softwaregravy/repro_active_support_i18n bundle exec irb require ''active_support/all'' detailed steps and error: 1) add to Gemfile require

Went to use ActiveSupport in a gem today and got an error on account of not having i18n installed. Either bundler should be installing i18n along with activesupport or docs need to be updated. quick repro: https://github.com/softwaregravy/repro_active_support_i18n bundle exec irb require ''active_support/all'' detailed steps and error: 1) add to Gemfile require

https://bugzilla.samba.org/show_bug.cgi?id=10977 Bug ID: 10977 Summary: Rsync path spoofing attack vulnerability (rsync 3.1.1 tested) Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=10936 Bug ID: 10936 Summary: Rsync path hijacking attack vulnerability Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org

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