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 actual file to the destination (rather than creating a symlink) and symlinks that point somewhere 'local' (i.e. to files which are part of the copy) will be copied as symlinks. However in practice when I set --copy-unsafe-links I still get warning messages. What should I be setting to get 'remote' symlinks to copy the referred file and 'local' symlinks copied as symlinks? -- Chris Green
On Wed, 2007-12-12 at 14:13 +0000, Chris G wrote:> 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.You have to additionally pass --links to make rsync copy the safe symlinks. This is mentioned in the "SYMBOLIC LINKS" section of the man page. Matt
Seemingly Similar Threads
- [Bug 13827] New: despite --copy-unsafe-links, rsync does not copy the referent of symlinks that point one level outside the copied tree
- option --copy-unsafe-links
- rsync 2.3.2 with --copy-unsafe-links work badly
- --copy-unsafe-links does not work for "double" symlinks
- [Bug 10989] New: "copying unsafe symlink" warning should not occur if file is not changing