similar to: [Bug 13827] New: despite --copy-unsafe-links, rsync does not copy the referent of symlinks that point one level outside the copied tree

Hi, as documented, if you use rsync with --copy-unsafe-links, and copy a directory with a symlink pointing outside of the copied tree, the referent of the symlink is copied. Now, assume that the directory contains a symlink, which points to a (2nd) directory outside of the copied tree. If this (2nd) directory contains another symlink, which also points outside of the copied tree, rsync

Hi, New to this list, but long-time (appreciative) user of rsync. Grateful for any help with my problem here... In particular, I've been having long-standing issues (just now getting around to trying to resolve them) when I use rsync with '--copy-unsafe-links' alongside the '--delete' parameter. If I use either of these two parameters in isolation (along with other shared

I'm running rsync 2.5.5 on a FreeBSD-CURRENT system. I have a directory that essentially is my web site, which I update when need be. I am (trying) to use rsync to sync a remote server with my changes whenever they are made. I'm using a little script to do this: #!/bin/sh DATA_DIR=/home/munish/data/www REMOTE_BACKUP=[snipped out user@host here] RSYNC_FLAGS="-zapuLxSC --stats

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Hi, in my backup script I'm using the "-L" option to transform symlinks into referent files/dirs. Now I'm also using the "--delete" option. Unfortunately "--delete" doesnt work if an error like "Symlink has no referent" occurs. So far the only solution for that seems to not use the "-L" option or to add "--ignore-errors". It

Hi All, I am using rsync to backup one server to another. I am connecting to the rsync daemon on the remote server and pulling to the backup server. When using SSH this error does not occur, but there are reasons why I have to use rsync directly. The problem I am having is that some of the symlinks on the remote machine will not copy. I am attempting to copy their referent by using the -L

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

https://bugzilla.samba.org/show_bug.cgi?id=14401 Bug ID: 14401 Summary: unicode character conversion problem from MacOS to Linux despite iconv Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=13920 Bug ID: 13920 Summary: --max-delete and dirs being replaced by symlinks on source Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne

https://bugzilla.samba.org/show_bug.cgi?id=3147 Summary: message 'copying unsafe symlink' only appears if verbose>=2 Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=10989 Bug ID: 10989 Summary: "copying unsafe symlink" warning should not occur if file is not changing Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=13364 --- Comment #3 from Chris Severance <samba.severach at spamgourmet.com> --- >enable munge-symlinks. That way the client will get back the same out-of-tree symlink as it started with This is a lousy option for backups. The only way to get my original links back is to pull the restore through rsync. Restoring directly from the rsyncd server

https://bugzilla.samba.org/show_bug.cgi?id=2395 Summary: problems copying from a dir that includes a symlink in the path Product: rsync Version: 2.6.4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

On Fri, Feb 17, 2017 at 12:33:28 +0100, Gionatan Danti wrote: > Hi list, > I would like to understand if, and why, the --unsafe flag is needed when > using --copy-storage-all when migrating guests which uses writeback > cache mode. > > Background: I want to live migrate guests with writeback cache from host > A to host B and these hosts only have local storage (ie: no

On 17/02/2017 19:50, Jiri Denemark wrote: > > Yeah storage migration should be safe regardless of the cache mode used. > Very good news, thanks. Let me be paranoid: is it *surely* safe? > > This looks like a bug in libvirt. The code doesn't check whether an > affected disk is going to be migrated (--copy-storage-all) or accessed > on the shared storage. > > Jirka

I presume the option --copy-unsafe-links really means to copy the file contents a symlink points to, even outside the tree being copyed, rather than make a symlink on the destination. What I find is that if a symlink on the source is dangling, that is, it points to nothing that exists, that symlink is not created at the destination. What I want is for all symlinks to be reproduced as symlinks

https://bugzilla.samba.org/show_bug.cgi?id=1599 Summary: copy-unsafe-links cann't take affect Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: faris.xiao@haoxi.com

This refers to version 3.0.0pre6 if that's relevant. I was expecting that if I specified the --copy-unsafe-links option to rsync that I'd then get no warnings about 'skipping non-regular file "bla/bla/bla"' but it doesn't seem to work like that. It *sounds* from the man page that if I set --copy-unsafe-links then symlinks that point 'elsewhere' will copy the

Hi list, I would like to understand if, and why, the --unsafe flag is needed when using --copy-storage-all when migrating guests which uses writeback cache mode. Background: I want to live migrate guests with writeback cache from host A to host B and these hosts only have local storage (ie: no shared storage at all). From my understanding, --unsafe should be only required when migrating

Hello, I try use rsync from Debian 2.2 (rsync 2.3.2) to mirror Debian distribution tree. in tree is directories dists/potato/main/binary-all/ dists/potato/main/binary-i386/ pool/ In directory dists/potato/main/binary-i386/ is some files symbolic links to ../binary-all/ and some links to ../../../../pool/ In mirror I want preserve links to binary-all/ and copy as files links to pool/. I try