Hello Reuti, thanks for your response. The problem occured when I had to move the shared folder where output files are wirtten from a NAS to an other. On the old NAS, everything was fine. I changed for a new one where rights management is different. I used the same CIFS mount for both NAS but on the ne wone the issue occured. For now, I have solved the issue by adding the noacl and noperm options in the CIFS mount but this is not satisfying since it is too much open. I have tried to managed the umask with a Starter Method but fails to make it work. It seems that whatever I do, the Starter Method is not launched. I have a single queue with a parallel environment. I set the Starter Method path in the qconf and tested the script that should be called (it works). However, the Starter Method is nerved applied (I added some touch of files in the Starter script to check whether it is launched or not). So, I don't know what is the best way to solve my issue. Do you have any advise?
Thanks in advance. Best regards. Lionel Spinelli - Ingénieur de recherche en bioinformatique UMR_S 1090 TAGC et UMR_S 1104 CIML Aix-Marseille Université - LUMINY - 163 Avenue de Luminy - 13009 Marseille Tél: +33(0)4 91 82 87 12 (TAGC) / +33(0)4 91 26 91 90 (CIML) Site : http://www.univ-amu.fr - Email : lionel.spine...@univ-amu.fr Afin de respecter l'environnement, merci de n'imprimer cet email que si nécessaire. ________________________________________ De : Reuti <re...@staff.uni-marburg.de> Envoyé : mardi 4 avril 2017 11:25 À : Lionel SPINELLI Cc : users@gridengine.org Objet : Re: [gridengine users] output file permission Hi, > Am 04.04.2017 um 09:52 schrieb Lionel SPINELLI <spine...@ciml.univ-mrs.fr>: > > Hello all, > > I have an issue with the permissions of the output file of my jobs. The > output file path is specified in the script through the -o option. The file > is created with umask 022 by the root (since SGE is run by root). Usually it's only created by the execd after it changed to the user who runs the job. Otherwise it would indeed be useless. > Then, the job starts using the submission user and fails because it cannot > open the output file due to permission issue (permission denied). And in fact > the file is "-rw-r--r-- root users". > The place where the file is created is a CIFS mount. I have search through > the internet for a solution and only found the one consisting in modifying > the umask through the starter method. Yes, the 022 is hard coded in the source. Some users allow others to write to the output files too, or have a distribution where each user is his own group too. > I have tried to set this started method in my queue with the script: Is this effect new in the cluster, or is it a new installation and fails instantly? -- Reuti _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
