similar to: are --temp-dir and --daemon mode compatible options

Dear rsync folks, I'd like to request/suggest that cli options to set TCP send/receive buffers be added to rsync client-side. Summary: I'm aware that a daemon's config-file can set socket options for the server side (e.g. SO_SNDBUF, SO_RCVBUF). That is useful. But when trying to get high-throughput rsync over long paths (i.e. large bandwidth*delay product), since

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

In the past there's been a need to provide consistency between symbolic links or repository metadata during a sync. Currently, rsync renames files piecemeal. The attached patch (extremely ugly) attempts to resolve this by foregoing the rename step until the end. It adds a new option (if we didn't, ls might catch up). There are several issues to get over. The first big one in

Updated to current cvs without the --exclude-from - patch. This patch allows specifying a --link-dest path similar to --compare-dest except that unchanged files are hard-linked to the --link-dest path instead of producing a sparse tree. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list members, there are two new rsync-features I made up and would like to discuss with you. If you think these new features might be useful for the whole rsync-community, please give me a note and I'll send you the patches (or post them here). 1.) Setting owner and/or group of backup files. In our servers I'm using rsync to backup

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

The attached patch adds an option --drop-suid which caused rsync to drop setuid/setgid permissions from the destination files. ie, even if the source file is setuid, the target file will not be. Added as we want to rsync the same files to machines both inside and outside our firewalls. For machines inside the firewall some files should be suid, for machines outside the firewalls they should

Included below is a shar archive containing two patches that together: 1) make backup files get their setuid and setgid bits stripped by default 2) add a "-s" option that allows backup files to continue to have these privileges This means that if you update a collection of binaries with rsync, and one or more of them has a local-root security problem, the backup file(s) created when

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]

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

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-

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hy folks, everybody knows, that rsync eats up a lot of memory, when rsyncing a lot of files. To avoid this i run rsync on different parts of the directory-tree (e.g. first ~muchofileuser/muchofilesdir1 then ~muchofileuser/muchofilesdir2 and so on) and it works fine for me. So i tried to do this in a automatical way (e.g perl/shell/whatever

Hello! In the attached file is patch for the option to set client connection limit. We had problem for dead hosts, so default system timeout is not enough. --conlimit option added Will be great to see this patch in the future version, so we do not need to patch every time. Thanks and Cheers, Eugene. -- -------------- next part -------------- diff -Naur rsync-2.6.8/errcode.h

Hi folks, we would like your feedback on a new option we have implemented. We would like to know whether it should be merged into the CVS tree. Perhaps one of the rsync developers can have a look at the code, improve it where necessary, and committ it to CVS. The name of the option is "--delete-mdays=DAYS" and it works in conjunction with the option "--delete." It modifies

In the bufferbloat age, anything that can make for a kinder, gentler bulk transfer protocol seems desirable. This add support for user and server selectable congestion control algorithms. As examples: --congestion-alg=lp # For the tcp-lp algorithm on the command line Or in a subsection: [mystuff] congestion alg = westwood # for a wireless connection And diffserv support: --diffserv=8 for

There's a rather old bug report in Debian's bug tracking system (see http://bugs.debian.org/27126) about wanting to be able to specify the maximum file size, as well as the minimum file size. Here's the text: Sometimes, it's useful to specify a file size range one is interested in. For example, I'd like to keep an up-to-date mirror of Debian, but I currently

In an effort to get my long-desired move-files functionality into rsync, I have created a version of my patch that runs as an extra pass at the end of the processing. This results in a simpler set of changes to rsync. I still think it would be nice to have incremental deletions during large transfers (as my first patch provides), but acceptance of this patch would relegate such quibbling to a

Martin, Just a minor fix. Jie, Try the -r option (or the --recurse) option instead. It looks like the source changed to this: options.c: {"recurse", 'r', POPT_ARG_NONE, &recurse}, But the help is still at: options.c: rprintf(F," -r, --recursive recurse into directories\n"); eric Jie Gao wrote: > > rsync: --recursive:

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