Hi Ward, You're right.
[root@node01 scratch]# pwd /scratch [root@node01 scratch]# ll total 0 drwx------ 3 root root 30 nov 21 13:41 1809 [root@node01 scratch]# ls -la 1809/ total 0 drwx------ 3 root root 30 nov 21 13:41 . drwxrwxrwt. 3 root root 18 nov 21 13:41 .. drwx------ 2 thais root 6 nov 21 13:41 .1809 -r--r--r-- 1 root root 0 nov 21 13:41 .ns But how can user write or access the hidden directory .1809 if he doesn't have read/write permission on main directory 1809? Thanks. -----Mensaje original----- De: slurm-users <slurm-users-boun...@lists.schedmd.com> En nombre de Ward Poelmans Enviado el: martes, 21 de noviembre de 2023 13:12 Para: slurm-users@lists.schedmd.com Asunto: Re: [slurm-users] slurm job_container/tmpfs Hi Arsene, On 21/11/2023 10:58, Arsene Marian Alain wrote: > I just give my Basepath=/scratch (a local directory for each node that is > already mounted with 1777 permissions) in job_container.conf. The plugin > automatically generates for each job a directory with the "JOB_ID", for > example: /scratch/1805 > > The only problem is that directory 1805 is generated with root owner and > permissions 700. So the user who submitted the job cannot write/read inside > directory 1805. If I look on our system, there should be hidden directory under that directory which is owned by the correct user. Our job_container.conf has: Basepath=/local Dirs=/var/tmp,/tmp,/dev/shm which gives directories like: /local/6000522/.6000522/_tmp/ The hidden one is owned by the user of the job. Ward
