Is it possible to force SLURM to have access to only job's running folder and not alter any other file?
I observe that when I run a SLURM job, it could create files on other folder paths and also could remove them. It seems dangerous that via SLURM job they can access others folders/files and make changes on them. $ sbatch run.sh run.sh: #!/bin/bash #SBATCH -o slurm.out # STDOUT #SBATCH -e slurm.err # STDERR echo hello > /home/avatar/completed.txt rm /home/avatar/completed.txt [Q] Is it possible to force SLURM to only have access to its own running folder and not others? Files access is controlled through UNIX permissions, so a job can only write where the submitting user has permission to write