-
Hi All, I have a situation on my compute cluster where TMPDIR is set to a value that works on most nodes but not all. I have to manually change the TMPDIR variable on a few select machines because the standard location is not available. I was hoping that I would be able to use a Is there any workaround other than exporting a new TMPDIR before running Thanks, Ed |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 11 replies
-
Self, you can do this:
And it will set the TMPDIR variable for you. It doesn't seem as though one can use a .env file for this purpose. |
Beta Was this translation helpful? Give feedback.
-
I love that The issue is that This would be very easy to configure though, we could add a setting specifically for setting the tempdir that just uses, like so:
Would that work for your use-case? |
Beta Was this translation helpful? Give feedback.
-
I think this is a great feature. But, in this case, I think the real fix should be in the cluster management. |
Beta Was this translation helpful? Give feedback.
I love that
just
has made it onto a compute cluster!The issue is that
.env
files change environment variables for child processes ofjust
, e.g. recipe lines and shebang recipes, but not forjust
itself. So if you setTMPDIR
in a.env
file or withexport TMPDIR := "/tmp"
, just will still use the old tempdir.This would be very easy to configure though, we could add a setting specifically for setting the tempdir that just uses, like so:
Would that work for your use-case?