Am 19.08.2011 um 19:54 schrieb Gowtham: > On Fri, 19 Aug 2011, Reuti wrote: > > | Am 19.08.2011 um 19:43 schrieb Gowtham: > | > | > <snip> > | > | If users want to check something on the nodes, they have to use `qrsh` > and get an interactive queue with a set "h_cpu 60" limit. > | > | > | > | -- Reuti > | > > | > > | > Thank you for your response. So far, the users who use SGE > | > submit via qsub (most of our programs are compiled with > | > MPICH2). Those who didn't use the SGE, made a list of > | > 'hot nodes' and put them in machinefile. then submitted > | > their jobs via mpirun > | > > | > The cluster has the following programs installed on it: > | > > | > # Crystal 2003 | 2006 | 2009 > | > # DMol3 > | > # Gaussian 1998 | 2003 | 2009 > | > # NAMD 2.8 > | > # Quantum Espresso 4.2.1 > | > # SIESTA 1.3-f1p | 2.0.1 > | > # SMEAGOL 1.0b > | > # VASP 4.6.28 | 4.6.31 | 5.2.2 > | > > | > and they have been behaving well with SGE so far. > | > > | > How would I tighten up the SSH screws so that their jobs > | > will run but won't be able to log into compute nodes? Is > | > it via /etc/ssh/sshd_config or some other such file? > | > | Yes, it's a line like: > | > | AllowGroups root operator > | > | on the nodes and put the admin staff in this additional group. > | > | MPICH2 since 1.3 has a tight integration into SGE by default. For Gaussian > it's necessary to adjust Linda_rsh to call a plain rsh instead of > /usr/bin/rsh, so that the rsh-wrapper will catch it and route it to SGE's > qrsh (in case you use Linda). > | > | -- Reuti > > > Thank you! And these edits in /etc/ssh/sshd_config go on > all the compute nodes, right? If yes, I could edit the > extend-compute.xml and have them in place for next > re-install.
Yep, just be sure that the groups exist to avoid locking out yourself. -- Reuti _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
