PathManager support for destinations on eos
Sadly lxbatch rather silently prevents (direct) writing to eos. While CAF doesn't see any issue, e.g., trying to write skims to eos the output file(s) will simply never show up, even when doing 'ls' from within the job right after the CAF application exits.
Since lxbatch has a somewhat special role we should therefore augment the PathManager to detect output paths on eos (target path starting with /eos/) and in that case change the copy command to eos cp local.file /eos/...
.
For reference: https://batchdocs.web.cern.ch/tutorial/exercise11.html
Edited by Ralf Gugel