Hi,
Am 12.12.2019 um 03:06 schrieb Brian Andrus:
> You prompted me to dig even deeper into my epilog. I was trying to access a
> semaphore file in the user's home directory.
>
> It seems that when the epilogue is run the ~ is not expanded in anyway. So I
> can't even use ~${SLURM_JOB_USER} to
You prompted me to dig even deeper into my epilog. I was trying to
access a semaphore file in the user's home directory.
It seems that when the epilogue is run the ~ is not expanded in anyway.
So I can't even use ~${SLURM_JOB_USER} to access their semaphore file.
Potentially problematic for a
Hi Brian,
can you maybe elaborate on how exactly you verified that your epilog
does not run when a job exceeds it's walltime limit? Does it run when
the jobs end normally or when a running job is cancelled by the user?
I am asking because in our environment the epilog also runs when a job
hits
All,
So I have verified that the Epilog script is NOT run for any job that times
out. Even though in the documentation (
https://slurm.schedmd.com/prolog_epilog.html), it states "At job
termination"
I guess timeouts are not considered terminated??
So, is there a recommended way to have a cleanup s
