No, the ofs.dirlist is there strictly for opendir() calls. The issue is
that xrdfs ls does a locate ahead of the opendeir() because it wants to be
nice and give you a composite directory listing. If the server is
unclustered this works just fine. If servers are clustered (i.e. headed by
a redirector) this usually works fine as well. The only case it breaks
down is wen the servers share a common file system. While the end results
is correct the whole process is very slow. We have a couple of ways around
this and will be implementing at least one of those to mitigate the issue.
Anyway, the default for ofs.dirlist provides full backward compatibility
(i.e. things work as before the introduction of eh directive).
On Tue, 30 Jun 2020, ivmfnal wrote:
> Hello. I am reading this thread and I want to make sure I understand it correctly that ofs.dirlist controls how "xrdfs ls" works - whether the request is handled locally by the redirector or by the client contacting each individual server directly ? Or do I get it wrong ?
>
> --
> You are receiving this because you modified the open/close state.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1174#issuecomment-651816557
—
You are receiving this because you commented.
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/1174#issuecomment-652005449",
"url": "https://github.com/xrootd/xrootd/issues/1174#issuecomment-652005449",
"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
