xrdfs ls :: allow listing with the same semantic as in shell

[adriansev]

Hi! It would be great that if ls is applied to a file to return a similar answer like in shell including for -l information on size and change time (currently for a file it responds with [3005] Unable to open directory)

[abh3]

Hi Adrian, Can you provide the case that you are using to elicit this error? Andy

…

On Tue, 2 Mar 2021, Adrian Sevcenco wrote: Hi! It would be great that if ls is applied to a file to return a similar answer like in shell including for -l information on size and change time (currently for a file it responds with `[3005] Unable to open directory`) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #1417

[adriansev]

@abh3 any ls on a file (instead of a directory) will throw this error. the use case was to check the existence of a file without the processing of the stat output.

[xrootd-dev]

OK, I have had a chat with Michal and indeed this is a defieciency in xrdfs. We will likely correct that in 5.1.1 but it will not be backported. Andy

…

On Tue, 2 Mar 2021, Adrian Sevcenco wrote: @abh3 any ls on a file (instead of a directory) will throw this error. the use case was to check the existence of a file without the processing of the stat output. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #1417 (comment) ######################################################################## 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

[adriansev]

great! thanks a lot! (also i got the message with backporting and i already started a discussion with relevant persons from collaboration. it will help tremendously an official post about the support status of the 4.x branch ;) )

[simonmichal]

This: c76cc29 should do the trick.

[simonmichal]

The patch has been released in 5.1.1.