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

XrdPosix: rename does not automatically replaces existing file #659

Closed
gganis opened this issue Mar 1, 2018 · 1 comment
Closed

XrdPosix: rename does not automatically replaces existing file #659

gganis opened this issue Mar 1, 2018 · 1 comment

Comments

@gganis
Copy link
Member

gganis commented Mar 1, 2018

This issue was discussed by email last summer but I realized that I never filled an issue in here.

According to the rename man page:
If newpath already exists, it will be atomically replaced, ...

However, this is not honored by XrdPosix::rename: if the target file exists the call always fails.

In the above-mentioned email exchange the reason for this was tracked back to the difficulty to accomplish a 'true' rename behavior when dealing with non-POSIX file systems.
As a possible 'partial' fix it was proposed to allow a 'true' rename as long as the existing target is neither remote nor symlinked.
Could this be implemented?

Gerri

@abh3
Copy link
Member

abh3 commented Mar 1, 2018

This has been addressed by commit 23adaf.

@abh3 abh3 closed this as completed Mar 1, 2018
ffurano pushed a commit to ffurano/xrootd-fbx4 that referenced this issue Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants