Print

Print

@simonmichal You are right, removing --path fixes the issue at hand.

The explicit --path is needed for writing to non-xrootd targets so it was added to all write operations. Other implementations don't automatically create paths so we can't completely remove this option. I'd have to start distinguishing between target types and would rather not do that. This is not a problem, I can wait until it is fixed upstream, running the old client until then.

Many thanks for your quick help!

.costin

—
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/1077?email_source=notifications\u0026email_token=AA7NRDQUWFAEDIGJQ6UFNZ3QRKQJNA5CNFSM4JGWSV2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXCEEQ#issuecomment-548282898", "url": "https://github.com/xrootd/xrootd/issues/1077?email_source=notifications\u0026email_token=AA7NRDQUWFAEDIGJQ6UFNZ3QRKQJNA5CNFSM4JGWSV2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXCEEQ#issuecomment-548282898", "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