similar to: log format '%P' only logs '/' when use chroot = true

Hi, I got the following report from a Debian user, about --files-from transferring the contents of a dir (i.e. including the files in it) specified in the input, even thugh the files aren't listed in the input. This happens only when the dir name ends with a slash. I asked him to cook up a script to reproduce this (as it wasn't quite clear to me at first what happened exactly). Any

The directory I'm trying to copy from is: /home/blah/dir The symlink is /home/blah/dir/unwanted_symlinked_dir On Fri, Mar 3, 2017 at 8:10 AM, Paul Slootman <paul+rsync at wurtel.net> wrote: > On Fri 03 Mar 2017, Steve Dondley wrote: > > > I'm trying to rsync a directory from a server to my local machine that > has > > a symbolic link to a directory I don't

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,

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

Ok it's now Solved ! In spite of trying all day long to figure it out what's wrong in my sintax i could find, ...using a pencile and a pice of paper, combining all commands parameters invoked so far and, came to the conclusion that -L does not stand with -l , think that i couldn't find in any docs or faq so far. Now, symlinks are being copied without a trouble. Tnks Paul for

I've just subscribed, but a search of the archive doesn't indicate this has been handled before... Is there a way to get rsync to not create a new file while transferring and then rename it, but to instead update the existing file in place, i.e. simply write those blocks that have been updated and leave the rest alone? That would be ideal for what I wanted rsync for, namely updating

Hy there, My name is Alex Vladulescu, and i found this very interesting tool for backup files and folders over remote network servers. For the past four days i have been reading the FAQ on the site, google-ing the web for some answers on my local problem, but i am very stuck, nothing seems to answer my question so far. My issue consists on having a rsyncd.conf on a master server on which i

OK, I packaged up the current CVS as our first preview release for 2.6.0. You can grab it here: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre1.tar.gz The MD5 checksum is: 70e9dea967f083c231b7821ef35aef1b rsync-2.6.0pre1.tar.gz There is not currently a .sig file for the package, but I'm looking into that next. Please test this and let me know if we have any remaining issues

Readers, I have tried the following command: rsync -t *.txt ssh user at remote.machine: and receive the following error: rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] My understanding of the manual is that the text files on my local machine should have been

[ 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's a bug reported in Debian about the tty being screwed up by wierd filenames, see http://bugs.debian.org/bug=242300 On the one hand, find will also do this. On the other hand, ls will replace such chars with a question mark. Upon inspection, it appears to be fairly simple to also do this in rsync (in the rwrite() function). Here's a patch. Opinions? Perhaps don't do it

I've run across a situation where I have a directory of .gz files. I do want to rsync this directory. I've tried without the --compress (because they are already compressed) but the files never get rsynced. Interactively, I get the following error: :rsync error: some files could not be transferred (code 23) at main.c(1045) In the /etc/rsyncd.log, for each of the files, I get:

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

Am 14.11.19 um 10:54 schrieb Paul Slootman via rsync: > You need to specify the source directory as the link-dest directory. Hi, I tried it also because it's an old question which has never worked for me. Instead it creates copies and not hard links: pierre at in94:~/tmp$ ls -li a b a: insgesamt 8 257315 -rw-r--r-- 1 pierre pierre 4 Nov 14 10:53 1 257316 -rw-r--r-- 1 pierre pierre 6 Nov

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

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

Currently sub(perl=TRUE) allows you to specify \U and \L in the replacement argument so that the rest of the subpatterns in the line (the \\<digit> things) will be converted to upper or lower case, respectively. perl also also has a \E operator to end these case conversions for the rest of the subpatterns (so they retain whatever case they had in the original text). For symmetry's sake

Hi, Could any one please tell me if there is any way to remove 11 letters long cryptic output from -ii option. I am using rsync 3.0.5 rsync -av -stats -ii --log-file-format='CONTENTS: %i %f %l %o %b' --log-file='/tmp/rsync-test' Mydocs/ Mydocs1/" The output of this command: 2009/03/31 15:15:17 [4537] building file list 2009/03/31 15:15:29 [4537] created directory Mydocs1

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