Re: Link-dest thinks file is newly created, but it isn't

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What does --itemize-changes say about that file? Try using the stat command on the various copies of it to see what is different about them. On 01/09/2015 09:42 PM, Clint Olsen wrote: Hi: I've been using rsync for a couple years now.

[Bug 10989] copying unsafe symlink warnings occur if nothing changed

https://bugzilla.samba.org/show_bug.cgi?id=10989 Jim Avera jim.av...@gmail.com changed: What|Removed |Added Summary|copying unsafe symlink|copying unsafe symlink

[Bug 10989] copying unsafe symlink warning treated as error, prevents --delete from working

https://bugzilla.samba.org/show_bug.cgi?id=10989 --- Comment #2 from Jim Avera jim.av...@gmail.com --- A much more serious problem is that when unsafe symlinks are copied pursuant to the --copy-unsafe-links option, they are all treated as I/O ERRORS. This prevents --delete from ever working. --

Re: Link-dest thinks file is newly created, but it isn't

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb k...@sanitarium.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What does --itemize-changes say about that file? Try using the stat command on the various copies of it to see what is different about them. In my original message, I

Re: Link-dest thinks file is newly created, but it isn't

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If it seeing the files as new then I agree that stat won't help. It might have explained some other itemize output. Since it is seeing the files as new then they must not be where it is looking. Meaning that your link-dest parameter must not be