Displaying 20 results from an estimated 50000 matches similar to: "Question about --copy-unsafe-links"
2019 Mar 09
2
[Bug 13827] New: despite --copy-unsafe-links, rsync does not copy the referent of symlinks that point one level outside the copied tree
https://bugzilla.samba.org/show_bug.cgi?id=13827
Bug ID: 13827
Summary: despite --copy-unsafe-links, rsync does not copy the
referent of symlinks that point one level outside the
copied tree
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity:
2002 Jul 03
1
option --copy-unsafe-links
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
2002 Apr 02
2
rsync 2.3.2 with --copy-unsafe-links work badly
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
2009 Oct 05
1
--copy-unsafe-links does not work for "double" symlinks
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
2014 Dec 06
3
[Bug 10989] New: "copying unsafe symlink" warning should not occur if file is not changing
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
2013 Aug 24
2
Potential incompatibilities between '--delete' and --copy-unsafe-symlinks' ???
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
2003 Jan 02
2
--copy-unsafe-links, links preserved in source tree or local directory?
Hi,
I'm a bit confused about what the '--copy-unsafe-links' option
considers the 'source tree'. In the man page it says that for links
pointing outside the 'source tree' the file will be copied, but when I
try this, for all links pointing outside of the local directory the
files are copied even though the links point to files that are in the
directory tree that is
2007 Apr 11
2
Rsync --Copy-links problem
Hi,
I am new to Rsync, but i have successfully used it to sync the contents
between two machines. Now the requirement is to sync the contents which are
symlinks. I need to sync the actual contents on client machine from these
symlinks.
I went through rsync tutorial and found --copy-links options to do my
job i.e, to transform symlink into referent file/dir
Issue:
Rsync Server : The actual
2003 Feb 22
1
simlinks and options
Greetings.
I wrote a script that make remote backups with rsync. I have 2 main
problems with it
1) I want that the destination directory (on the repository machine)
recreate the backed up file path and it permission (I use -R here )
2) Is there a way to "follow" all the links using -R and -a parameters..??
Currently I am using something like this.
rsync -al --delete
2004 Aug 18
0
[Bug 1599] New: copy-unsafe-links cann't take affect
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
2002 Dec 13
2
Problem with absolute symbolic links
I'm trying to synchronize a particularly troublesome directory structure on a SunOS box to a PC. I really want all symbolic links resolved to real files on the PC when everything is done. I can't seem to find any combination of parameters that will accomplish this.
It boils down to two problems.
1. It seems like that even if I exclude a symbolic link that is a directory it is not
2005 Oct 06
0
[Bug 3147] New: message 'copying unsafe symlink' only appears if verbose>=2
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
2017 Feb 17
2
Unsafe migration with copy-storage-all (non shared storage) and writeback cache
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
2018 Feb 28
2
Wide links and insecure wide links
Thank you.
So, If I understand correctly, "ordinary" "wide links = yes", means Samba
*will* traverse an existing symlink that points outside the root of the
share, if permissions allow. However because it *also* disables SMB1 Unix
extensions, it *also* prevents the user from creating or modifying symlinks
on the share, so in wffect it inherently prevents this being
2016 Mar 17
1
[Bug 11800] New: smarter "safe" symlink detection
https://bugzilla.samba.org/show_bug.cgi?id=11800
Bug ID: 11800
Summary: smarter "safe" symlink detection
Product: rsync
Version: 3.1.1
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: core
Assignee: wayned at samba.org
2004 Jan 24
2
[PATCH] --links-depth for rsync
Hello,
about a year ago I ran into situation where there's a "metadirectory"
containing directories and symlinks to files. There was a need to mirror
the contents of files and directories gathered via symlinks to this
metadirectory, regular mirroring of the tree wouldn't do any good.
The attached patch gives the user ability to define how many symbolic
links rsync should follow
2005 Jan 27
1
rsync clobbering links?
When using rsync -avv to recursively copy a local directory on a
remote server, and if the remote server has a symbolic link of the
same name pointing to some other directory, then that remote symlink
is clobbered in favor of the hard-wired path. I looked at the man
page and other rsync documentation about copying links, but not of the
options seemed to apply in my case. The closest was
2007 Nov 10
3
Funny issue with chroot + symlink outside chroot
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
2015 Jan 23
4
No symlink support on SMB2 and SMB3?
Hello,
I am using Samba version 4.2.0rc4-GIT-4701d74.
When using a connection in protocol smb2 or smb3, the unix client says
symlinks are not supported, for example:
# mount //ip.addr/Programs ./tmp -o vers=3.0
# cd tmp
# ln -s bla blub
ln: failed to create symbolic link ?blub?: Operation not supported
# mount
//ip.addr/Programs on /mnt/tmp type cifs
2002 Mar 08
1
delete fails to delete everything it should like dangling symlinks
I think someone posted this before, but I can't find it in the archives.
I am using rsync to pull down source files to be compiled. The delete
options are used to clear out any old files left over from previous.
Normally this works. I've run into one case where it persistently fails.
Within the directory created during compiling is a symlink to another
directory, also created during