similar to: Man page suggestion: organize options into sections

One thing that's bugged me is that some of the man page lines in the options summary are longer than 79 chars and wrap onto the next line. These are just one line summaries (detailed description appear later) so they can, and should, be terse. Here's an edited diff showing my proposed changes (and a 79 char ruler):

https://bugzilla.samba.org/show_bug.cgi?id=4037 Summary: Rsync should obey --keep-dirlinks when searching basis dirs Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Wayne, Attached is a patch worth of suggested man page improvements for --no-implied-dirs and --keep-dirlinks. I think new users would find my explanations clearer and more complete, although you may want to make additional changes. I regenerated rsync.1 and the patch includes changes to it, but my yodl is somewhat weird, so I suggest you run yodl again yourself. -- Matt McCutchen

Hi, I have the following script that I'm writing to backup my gentoo linux system. ----- start of script ----- #!/bin/sh # # RSYNC_OPTS="--archive --one-file-system --perms --executability --progress --stats --delete-after --hard-links --keep-dirlinks --verbose --inplace" RSYNC_USER="bs" RSYNC_SERVER="192.168.6.6" RSYNC_MODULE="ben-desktop"

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

https://bugzilla.samba.org/show_bug.cgi?id=5370 Summary: sockopts attempts to set options after the socket is open Product: rsync Version: 2.6.9 Platform: x86 URL: http://people.freebsd.org/~gordon/rsync-socket.diff OS/Version: Linux Status: NEW Severity: normal Priority: P3

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

Hi, the combination of --keep-dirlinks and --delete (--delete-during, --delete-delay) erroneously deletes symlinks to directories on the receiver. With --delete-before and --delete-after it works as expected. (rsync version 3.0.3 protocol version, on Debian Lenny) I don't think that this behaviour is intended. Details/example: - Host 1 directory-structure: drwx------ ./1

Looking at http://rsync.samba.org/ftp/rsync/patches/fileflags.diff -- It looks like the changes from fileflags-fixes.diff patch were applied to the patch from http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz , but this entire chunk of the that original diff file was lost: > diff -up a/config.h.in b/config.h.in > --- a/config.h.in > +++ b/config.h.in > @@ -64,6 +64,9 @@

Hello folks, trying to make use of the new --keep-dirlinks feature for a synch port; it works excellent but feels incomplete without a way for rsync to ignore recursive links. Example: # ls -la . total 6 drwxrwxr-x 2 bldmstr staff 512 Aug 16 21:42 . drwxrwxr-x 8 bldmstr staff 512 Aug 16 21:41 .. lrwxrwxrwx 1 bldmstr staff 2 Aug 20 12:07 bogus -> .. if you use

Hello, I'm trying to push some data from one machine to another via rsync source machine uses rsync 3.0.8, it's a CentOS 5.6 Linux with rsync 3.0.8 package from rpmforge destination machine uses rsync 3.0.6, it's a Scientific Linux 6.0 with rsync 3.0.6 from its repository destination machine is running a rsync daemon with the following configuration: log file = /var/log/rsyncd.log

I've been using the --keep-dirlinks feature of 2.6.3pre1. I also use -x (--one-file-system) and --delete-after. The symlinked directories on the receiver are symlinked to a partition other than the one where the target of the rsync resides (that's the whole point of this nifty --keep-dirlinks feature). I discovered that the symlinked directories are not being processed for deletions.

https://bugzilla.samba.org/show_bug.cgi?id=5601 Summary: extend --keep-dirlinks to files also Product: rsync Version: 3.0.2 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: hendrik.maryns@uni-tuebingen.de

Hi, A minor bug in the manpage was noticed by a Debian user... (Please keep the 418923-forwarded@bugs.debian.org in the Cc list in replies.) diff -u -r1.399 rsync.yo --- rsync.yo 23 Jan 2007 15:34:43 -0000 1.399 +++ rsync.yo 12 Apr 2007 19:30:17 -0000 @@ -724,7 +724,7 @@ also ignored. Using this option in conjunction with bf(--relative) may give unexpected results. -dit(bf(-K,

If I have a backup script that does the following: (latest 2.6.9 rsync) rsync --archive --hard-links --force --ignore-errors --numeric-ids --keep-dirlinks --delete / /backup I've found that if there is a symlink in place that gets backed up (which goes fine), i.e.: homelink -> /home/ and then that symlink gets changed into an actual directory, i.e.: rm homelink mkdir homelink rsync

It would be nice if rsync offered a way to specify individual dirlinks to keep without keeping all dirlinks. (Unison can do this.) For example, consider the following command: rsync -a --relative src/./ dest/ If rsync refrained from trimming a trailing /. off of source arguments (at least as an option), one could keep a dirlink by passing it as an additional source argument with a /. and

Hi folks, I have a bunch of directories to mirror via rsync. I have lots of hardlinked files spread about these directories. Therfore I use -R (--relative) and -H. so far ok but: I create symlinks to the source-directories via script because src-dirs have changing names (date and time of backup) and I want to have constant directory names on target. How can I achieve that? I thought -k

Hi, I have gone through the rsync documentation and also tested same both --no-implied-dir and --keep-dirlinks options. My question is what is the difference between these options in below scenario? I have /foo/bar is the symlink to /foo/baz at source and same directory structure with symlink is there at destination. When I sync the data from /foo/bar/* with --relative option specified, I am

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

rsync's -v is fairly useless. Learn to use -i instead or in addition to. On 2/4/24 12:58, Andreas Gruenbacher via rsync wrote: > Hello, > > when trying to rsync files between hosts, I ran into a surprising case > in which rsync replaces a symlink with a directory, with no indication > of any kind. > > In the following reproducer, rsync is called as follows: > >