I am guessing that you are running VMs in the cloud, maybe even Azure.
By default, they set /tmp to 0700 when the node is deployed. It is up to
you to change that as needed as part of the cloud-init or other finalize
step.
I took to creating /tmp/scratch with permissions of 1777 and then
symlink that to /scratch which is where users are directed to.
You could just do "chmod 1777 /tmp" as well
Caveat: If this is the ephemeral ramdisk/ssd/etc disk that is created
each time the node starts up, you have to do the above step every boot.
Brian Andrus
On 2/2/2022 8:59 PM, William Zhang wrote:
Hi ,
My slurm version is 20.11.5 .
I use job_container/tmpfs to set up a private /tmp ,but the
permission is 700. Normal user can not read or write.
drwx------ 2 root root 6 Jan 31 01:32 tmp
I think the permission should be 700 ,or the owner of the directory
should be the user which run the job.
slurm.conf
JobContainerType=job_container/tmpfs
TmpFS=/tmp
job_container.conf
NodeName=g0025 AutoBasePath=true BasePath=/ram2
findmnt
