Hi Oliver,
No the TID should not have spaces not any other character that is invalid
for a Unix ID. So, I am wondering where that is being injected into the
system as the TID is normally "cleaned".
Andy
On Sat, 27 Jun 2020, Oliver Freyermuth wrote:
> Hi Andy,
> actually, I'm now using this`to explicitly get the last component of the output, which also seems to work well:
> ```
> while read -r -a line; do
> # Default format is: "TID OP MODE LFN", note TID may contain spaces.
> # Just take last column!
> num_cols=${#line[@]}
> LFN=${line[$((num_cols - 1))]}
> chmod go+rX "${LFN}"
> done < /dev/stdin
> ```
> So this fixed my issue, and redefining the format would likely fix it, too (i.e. this is now "WORKSFORME"). I still wonder if the TID containing spaces is a wanted behaviour, though. If that's acceptable, we can close the issue, but if the TID should never contain spaces, we should probably keep it open to fix that.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1200#issuecomment-650596703
--
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/1200#issuecomment-650698287
########################################################################
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
