Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

honour --update for symbolic links #141

Open
twojstaryzdomu opened this issue Jan 22, 2021 · 1 comment
Open

honour --update for symbolic links #141

twojstaryzdomu opened this issue Jan 22, 2021 · 1 comment

Comments

@twojstaryzdomu
Copy link

twojstaryzdomu commented Jan 22, 2021

rsync 3.2.3 will only copy, not update, symbolic links, without regard to their timestamps on the receiving end. There is no option to support preserving more recent links with '--update' on the receiving end.
I'm using symbolic links to 'black out' links by linking to /dev/null in a repository that includes files that have to be deleted.
The problem is more recent symbolic links on the target tend to get overwritten when a source running an update transfer overwrites the newer symbolic link with a prior, less recent copy of (by link's mtime) symbolic link. I find no option to honour the mtime of the newer symbolic link during an update transfer. Symbolic link time stamps on modern file systems are well supported and no different from regular files.
Please add an option that would have ' --update' behave for symbolic links exactly like for regular files i.e. skip source links if their target counterpart is newer (by mtime).

@twojstaryzdomu
Copy link
Author

twojstaryzdomu commented Jul 3, 2021

The PR #198 fixes this issue, albeit with a slight change.
Due to the risk of impacting the existing behaviour of the '--update' switch, which some users may rely on or find convenient, the symlink update mode is enabled independently via the '--update-links' switch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant