Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] Transferring PreCmd and PostCmd while retaining non-transfer behavior?
- Date: Fri, 08 Feb 2019 23:44:54 +0000
- From: Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: [HTCondor-users] Transferring PreCmd and PostCmd while retaining non-transfer behavior?
Per the manual, you have to input-transfer your PreCmd and PostCmd scripts since they're executed out of $_CONDOR_SCRATCH_DIR. But by enabling the file transfer your job winds up running in the scratch space, rather than the directory from which it was submitted. What's the proper way to revert a submission back to running in the submitted directory via a shared filesystem, but while still using transferred PreCmd and PostCmds?
For system-supplied commands, I've done MY.PreCmd = "../../../../../../bin/mv" or the like, but I won't necessarily have a priori knowledge of where the custom scripts are located.
Michael V. Pelletier
Information Technology
Digital Transformation & Innovation
Integrated Defense Systems
Raytheon Company