@abh3 So, i would like to have a clear picture of the interplay of export, localroot and namelib name2name declarations.
So, AFAIU the name2name setting prepend to the queried path the site level setup of name2name (and maybe remove it if found in the path?) so this is a somehow external way to re-base all accesses to a certain path.
Now, the problem is with export and localroot ... AFAIU the localroot is used when using oss.space declaration to gather together all physical space into a single symlink based namespace. but if i want to just export a single mount point the oss.space is not used, so the localroot should be similarly not used and i would expect to just all.export /my_single_mountpoint , the problem in this case is that name2name is prepended to /my_single_mountpoint instead of appended. My strong suspicion is that i do not understand what all.export means and that it does not refer to a physical path. So, could you please shed some light on this, and what is the way use a single mountpoint?
Thank you!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1358#issuecomment-753813496", "url": "https://github.com/xrootd/xrootd/issues/1358#issuecomment-753813496", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1