This doesn't looks like a xrdfs problem but rather like a server side problem. for example:

$ hostname -f
cent7a.slac.stanford.edu
$ which xrootd
/bin/xrootd
$ xrootd -version
v5.0.3
$ xrootd

On another host, i run

$ xrdfs cent7a.slac.stanford.edu ls /tmp |wc -l
130
$ xrdfs cent7a.slac.stanford.edu ls -l /tmp | wc -l
5

the "ls -l" only shows a few dirents. The same tests against a xrootd 4.12.1 server gives consistent result.

—
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/1340", "url": "https://github.com/xrootd/xrootd/issues/1340", "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