similar to: --no- usage

>From the manpage: --csum-length=LENGTH By default the primary checksum used in rsync is a very strong 16 byte MD4 checksum. In most cases you will find that a trun- cated version of this checksum is quite efficient, and this will decrease the size of the checksum data sent over the link, mak- ing things faster. You can choose the

This is a patch against the manpage to clarify what the --perm option does and does not do. Paul Slootman -------------- next part -------------- diff -ru orig/rsync-2.5.6/rsync.1 rsync-2.5.6/rsync.1 --- orig/rsync-2.5.6/rsync.1 2003-01-28 04:11:57.000000000 +0100 +++ rsync-2.5.6/rsync.1 2003-03-07 12:18:19.000000000 +0100 @@ -562,8 +562,13 @@ default\&. .IP .IP "\fB-p,

In the manpage, all occurrences of a single quote (or apostrophe) are preceded by a backslash. This means that these get turned into acute accents by groff; here's the relevant part of the groff manpage: \' The acute accent ; same as \(aa. Unescaped: apostrophe, right quotation mark, single quote (ASCII 0x27). I think all these backslashes should be removed, as the

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,

[ see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426191 ] The text in the description of the --append option may lead one to believe that files that are shorter on the receiving side won't be updated, due to the following text: ... Only files on the receiving side that are shorter than the corresponding file on the sending side (as well as new files) are sent. ... IMHO

There are a couple of bug reports on the Debian rsync package about problems with a recipient filesystem that can't cope with all possible unix filenames. Notably filenames with question marks are a problem... I guess that people are trying to backup systems to a SMB share which presumably is then regularly backupped to tape. This basically sounds like a reasonable thing to do :-) Would

I'm using 2.6.3pre1 to transfer a rather large Debian archive (126GB, more than 30 million files). It contains about 450 daily snapshots, where unchanged files are hardlinked between the snapshots (so many files have hunderds of links). It's been running for some time now, and I found that while it's far from done, it's already used 165GB on the receiving end. Investigation shows

A trailing slash on a module name has no effect, which is on the one hand logical as it's not a directory name; on the other hand it's not consistent either (as experienced by a user). I suggest at least adding some comment to the manpage where trailing slashes are discussed. Perhaps also mention it in the rsyncd.conf manpage, where perhaps it may be noticed sooner. If I find the time

I wanted to restrict rsync to listen only on one IP address on a multi-homed system. I put an "address aa.bb.cc.dd" option in the (single) module definition, as the manpage shows that "address" is a module option, not a global one. However, lsof showed that rsync had bound to * instead of the specified IP address. Moving the "address" line to the global part did the

I just received this bug report on Debian's rsync package. I've verified it. The entry from the manpage: -C [...] Finally, any file is ignored if it is in the same directory as a .cvsignore file and matches one of the patterns listed therein. Here the patterns of a .cvsignore file is apparently used to exclude file outside the directory where the .cvsignore file is found. Any

There are one or two open bug reports in the Debian bug tracking system that boil down to being able to specify the order files are trasferred. One example where this is useful is to first transfer the packages, then the list of packages. That means that the available list of packages is always consistent, without any packages listed being temporarily unavailable. I'm sure Wayne knows this

Two patches: one to correct the spelling of permissions (in comments, but such typos disturb me as well), and one to cast inode and dev to unsigned long before comparing, to prevent gcc giving a warning "comparison between signed and unsigned". Paul Slootman -------------- next part -------------- diff -ru orig/rsync-2.5.6/generator.c rsync-2.5.6/generator.c ---

Hi @all! I have two questions: - First, am I right that the chance of getting the same 32-bit rolling checksum is 1/2^16 and to get the same 128-bit MD5 Hash is 1/2^127? - Finally I want two know if it is possible to change an amount of blocks manually? e.g. I made a 100 MB file with "dd if=/dev/zero of=/home/test.xyz bs=1M count=100" and know I want to change, lets say, 10 blocks of

I've been using 3.0.0pre8 to move a Debian archive from one filesystem to another. This archive contains a daily snapshot of the Debian ftp site, with common files hardlinked to save space. I noticed that it was using far more space than necessary. Upon investigation it seems that all the source files that have inode numbers greater than 2^31 aren't being hardlinked together at the

On Mon 07 Apr 2008, S.A. Birl wrote: > > Server is running rsync 2.6.1 on RH > Client is running rsync 2.6.3 on Cygwin (Win2003) > > When I connect client to server, I get kicked out after SSH > authentication. I can manually ssh into the server with no problems. Is the server running an rsync daemon? If so, why the ssh? Paul Slootman

I just noticed, too late )-: --append This causes rsync to update a file by appending data onto the end of the file, which presumes that the data that already exists on the receiving side is identical with the start of the file on the sending side. Any files that are the same size or shorter on the

added: --no-compare-xattrs --no-compare-extra-stats --no-compare-perms --no-compare-uids --no-compare-times to ignore specified files informations when comparing. The current strategy to disable comparison on file informations is to flatten data structure so they return the same 0/NULL value on comparison and be, in fact, ignored to determine if the files differ. This patch preserve original

Hello all, I am using rsync 2.6.3 on RH 9 Linux systems. I think everytime I run the rsync command, all the files get transferred even if they haven't changed. Rsync is running as a daemon on my server. Below is the /etc/rsycnd.conf from my server: [ftpscript] path=/home/gab/ftpscript comment=My FtpScript list=yes On my client I use the following command: /usr/local/bin/rsync

The subject says it all :-) Apparently in pre-3.0.0 versions '%P' would log the actual path as specified in the module entry in rsyncd.conf, but now it's apparently relative to the chroot... Paul Slootman

I'm adding a new escape to log-format, %s, to print out the checksum of a file, and I've got a couple problems. They've got to be simple bugs, but I haven't been able to figure them out. The following patch gives me a broken pipe and a bus error when I test it. Note that I've applied the md5 patch beforehand. diff -Naur rsync-2.6.5-md5/log.c rsync-2.6.5/log.c ---