 |
 |
'ls' doesn't seem to give reasonable explanation about error when existing file name is used as argument (it expects directory name only): ``` $ xrdfs eoscms.cern.ch ls /eos/cms/store/group/upgrade/Tracker/L1Tracking/Synchro/Input/Muon/RelValSingleMuPt100_CMSSW_6_2_0_SLHC26-DES23_62_V1_LHCCRefPU140-v1/E4437F74-3C2F-E511-8913-0025905B85EE.root [ERROR] Server responded with an error: [3011] Unable to open directory /eos/cms/store/group/upgrade/Tracker/L1Tracking/Synchro/Input/Muon/RelValSingleMuPt100_CMSSW_6_2_0_SLHC26-DES23_62_V1_LHCCRefPU140-v1/E4437F74-3C2F-E511-8913-0025905B85EE.root; No such file or directory ``` Though, the file exists locally on the system and is accessible via xrdcp. While document provides simple explanation of using "ls" versus "stat" It might be not obvious for all users 'ls' is for directory listing only and "stat" for getting info about the file or directory: http://xrootd.org/doc/man/xrdfs.1.html We suggest either note in manpages that performing "ls" on something that is not a directory has undefined behavior or make it clear to user when srderr is thrown if he/she is expecting directory listing and NOT getting information about the file. Or other better explanation of difference... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/403 ######################################################################## 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