You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@weiyuan-jiang There might be a simple "fix" for discover (e.g., not NAS or local machines).
It turns out both LOCAL_TMPDIR and TSE_TMPDIR exist on login nodes! So, what we might just do is near the top of gcm_setup say "If discover, setenv TMPDIR=$LOCAL_TMPDIR".
Then, mktemp will use that and that does not have the noexec bit that /tmp has set.
For NAS, we'd need to think but then again, we've never really had this issues at NAS. But if we did, I can sort of think of ways to work around that even there.
Some users got issues when executing a file in the temporary directory.
GEOSgcm_App/gcm_setup
Lines 2606 to 2610 in 4ceccc3
I suggest to execute the command directly without writing to a file
The text was updated successfully, but these errors were encountered: