Reuti, On Sat, Apr 16, 2016 at 6:08 AM, Reuti <[email protected]> wrote:
> Hi, > > Am 07.04.2016 um 23:15 schrieb Michael Stauffer: > > > SoGE 8.1.8 > > > > Hi, > > > > I'm trying to figure out how to allow users to submit qsub jobs from > qlogin sessions and from other qsub jobs, while preventing starting qlogin > sessions while within a qlogin session, and preventing poorly-written > scripts from running out of control recursively and submitting a dangerous > number of jobs. That is, I'd like to allow a initiating single level of > qsub calls from exec hosts. > > > > I can think of some hacks to do this, but am wondering if there's an > official way? > > > > For qlogins, to prevent calling qlogin from qlogin session: I could > check the job spool 'environment' file during login, and if QRSH_PORT is > not the head node, I can logout of the new session. Or even more easily, I > could write a wrapper for qlogin that checks that it's being called from > head node. > > For `qlogin` these settings are used: > > $ qconf -sconf > ... > qlogin_command builtin > qlogin_daemon builtin > > As these are not only global settings, they can be changed for each > particular machine. For each exechost it could be changed/created to read: > > $ qconf -sconf nodeXY > qlogin_command /bin/false > Thanks for the reply. I'm finally getting back to this question. Although this would work, I think I'll simply check the QRSH_PORT var in the qlogin environment to see if it's originated from head node or not. Then I can print a clean error message. -M
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
