Huh? That this is certianly not one that xroot would ever conjure up. If
this is being generated by EOS then it's an EOS problem and this should be
refered to them. In native xroot land, the tid *never* has spaces exactly
for this reason.
On Tue, 19 May 2020, Oliver Freyermuth wrote:
> I just encountered in real life that the event stream default "notifymsg" for `chmod`:
> https://github.com/xrootd/xrootd/blob/cfdc6aca0bde74f7b65000987f846512c42a87ab/src/XrdOfs/XrdOfsEvs.cc#L139-L141
> produces something not cleanly parseable, The reason is that the {{TID}} may contain spaces, such as {{Robot: ATLAS Data Management}} does, and worst case this might also happen with the path.
>
> Since I'm only interested in the {{LFN}} anyways, I'm now just looking at the last column in my script (hoping the path does not contain spaces), but I wonder if the format should be changed in general (enquoting the separate tokens? escaping spaces? Using {{\t}} or {{\0}} to separate the tokens?).
>
> --
> 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
—
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/1200#issuecomment-631185938",
"url": "https://github.com/xrootd/xrootd/issues/1200#issuecomment-631185938",
"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