similar to: File that "vanish"es between readdir and stat is not IO error

Hi, The problem I found is not in what rsync, but on the error handling: How to reproduce: On server side I setup a tree and share using rsync + xinetd, of course, for security reason I use chroot option. Now I push this symlink: lrwxrwxrwx 1 root root 4 nov 10 16:28 horsroot -> /bin/ Now I try to do: ./rsync -avPH --copy-unsafe-links draco::test/ /tmp/rsyncdest/ (Of course the

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

I came up with a patch to fix the problem of IO Errors caused by excluded files as did Eugene V. Chupriyanov below. Is there a chance that this change will show up in a future version of rsync? Is there a reason that we should not ignore IO errors when copy_links is off? Just want to make sure that I'm not missing something here that may corrupt my syncs.... Here's the version that

Hi, when syncing from windows NT/cygwin to linux usimg rsync 2.5.2 I get the following error: readlink pagefile.sys: Permission denied IO error encountered - skipping file deletion pagefile.sys is however in the exclude-list, so I think rsync shouldn't care that it can't stat the file. The code fragment responsible is if (readlink_stat(fname, &st, linkbuf) != 0) {

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

https://bugzilla.samba.org/show_bug.cgi?id=3653 Summary: Silence 'vanished files' messages Product: rsync Version: 2.6.8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: count-samba@flatline.de

https://bugzilla.samba.org/show_bug.cgi?id=4899 Summary: When a mounted dir cannot be visited, rsync will halt there and the shell is halted, even "ctrl -c" can't quit it. Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal

A new 2.6.0 feature is supposed to use a different exit code when the only 'errors' were from files that disappeared between the building of the file list and the actual transfer of files. But if the client is local and the server is remote, IOERR_VANISHED gets set on the remote server, but is never passed to the local client (the io_error value is passed at the end of the file list, not

As mentioned on the rsync home page, the --files-from=FILE option in rsync version 2.6.0 is a useful option that allows one to "specify a list of files to transfer, and can be much more efficient than a recursive descent using include/exclude statements (if you know in advance what files you want to transfer)". However, --files-from does not help one implement the --rsync-exclude=FILE

I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

https://bugzilla.samba.org/show_bug.cgi?id=3649 Summary: buffer overflow in receive_file_entry Product: rsync Version: 2.6.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: sambesselink@planet.nl

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

Dear friends! I really appriciate the great job you did on rsync package and hope for its further improvement and development. It works great in our pretty complex environment and helps us a lot in our daily duties. But we've run into couple of small inconveniences. First one: We use rsyncd to propagate a tree of html files among several web-servers. That files are generated on the fly and

Hi, Wouldn't you know, I can't get rsync to throw an error during a copy. :) I need to put together some instructions for a guy that runs a WISP for him to look over before weekly backups are made (I'll be copying the files to /dev/null so any read errors can be caught). I can do the simple : rsync warning: some files vanished before they could be transferred (code 24) at

hello, does somebody know how to circumvent that "extra file access restriction feature" introduced in osx some time ago ? i already tried adding rsync binary to programms with "full disk access" privilege ( system-prefs -> security & privacy -> privacy -> full disk access)? , since running as root is not sufficient - but it does not work. i want to make sure

We use rsync in a Linux installation script. First, the root filesystem of another machine on the network is cloned with "rsync -axzH", and then a few files are updated to give the clone its own identity. This works fine, but last week, the Postfix mailer daemon on a new machine refused to start because some lock files had a link count of 2. It turned out that rsync had created two

Hi! This problem gave me quite a headache tonight... I more or less have this source directory: hop@krautesel:/var/tmp$ ls -laR from/ from/: total 12 drwxrwxr-x 3 hop hop 4096 Feb 8 03:34 . drwxrwxrwt 6 root root 4096 Feb 8 03:34 .. drwxrwxr-x 2 hop hop 4096 Feb 8 03:18 CVS -rw-rw-r-- 1 hop hop 0 Feb 8

Hello List I've been running this command, with the accompanying error: [root at mythtv ~]# ssh -t rsync at 192.168.1.40 sudo rsync -avzAXH --delete-after -e /home/rsync/bin/rsync_ssh /home/ root at 192.168.1.100:/mnt/bigdisk/morgansmachine/home root at 192.168.1.100's password: building file list ... rsync: readlink_stat("/home/morgan/.gvfs") failed: Permission denied (13) done

All, During development of a backup solution with rsync I experienced some failed backups because of RC 23, partial transfer. These were because the application using the data I was backing up, was still active, and had deleted a file inbetween rsync compiling the file list and then transfering the file. After some feedback from Wayne Davidson and JW Schultz suggesting the solution to this,