You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: