Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dcache-core,dcache-xroot,dcache-bulk,dcache-frontend: resolve path pr…
…efixes and paths for symlinks Motivation: https://rb.dcache.org/r/13937/ master@51594993ee1ac88d8b8ad350788f5153e0665b98 and https://rb.dcache.org/r/13923/ master@c491f2d312abcbadefcf1df2af85c5620e1e1867 introduced support for relative paths in the Frontend/Bulk requests and in the xroot door, respectively. It did not consider, however, the case when path prefixes may themselves involve symlinks. This could happen either by a symlink in the configured prefix from the door or user root, on in the prefix part of the actual target. Modification: Since https://rb.dcache.org/r/13908/ we have the stored procedure and PnfsManager support for resolving symlinks. This patch adds a PnfsMessage and uses the PnfsHandler to ask for resolution of the symlinks in the Frontend and xroot doors; in addition, symlink resolution is done on the paths of the initial targets given to the Bulk service when they are processed. Result: The support for both absolute and relative paths does not fail if there are symlinks affecting the path prefix. Target: master Request 9.0 (partial -- for frontend) Patch: https://rb.dcache.org/r/13971/ Requires-notes: yes (for 9.0) Acked-by: Tigran
- Loading branch information
Showing
14 changed files
with
188 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.