Re: [HTCondor-users] Job TMP environment variable

[Thomas Hartmann <thomas.hartmann@xxxxxxx>]

Hi Petr,

maybe a job transform could work to manipulate a job's environment [1]

But maybe you can catch such cases with a bind mount? E.g.,
  # on each batch node
  MOUNT_UNDER_SCRATCH = /tmp, /var/tmp,
would mount for each job both paths in each job's scratch dir.
Advantage imho is also, that the tmps-in-scratch are cleaned up with the 
job's termination.
But if your job home volume has not as much space available as the 
generic TMP dirs, jobs could maybe get into space trouble, when they 
would blow up their TMPs.

Cheers,
  Thomas


[1]

# ad hoc - not tested...
# on the scheduler

JOB_TRANSFORM_NAMES = $(JOB_TRANSFORM_NAMES), SETENVTMPS
JOB_TRANSFORM_SETENVTMPS @=end
[
eval_set_environment = "TMP=/tmp TEMP=/tmp"
]
@end


On 21/12/2020 22.13, Petr Vokac wrote:
> Hi,
>
> Is there a way to set job environment variables TMP, TEMP, TMPDIR to
> /tmp (vanilla universe, no containers)?
>
> Petr
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature