Am 19.09.2012 um 09:45 schrieb William Hay: > On 18 September 2012 21:37, Reuti <[email protected]> wrote: >> Am 18.09.2012 um 18:31 schrieb Dave Love: >> >>> Reuti <[email protected]> writes: >>> >>>> Am 17.09.2012 um 20:28 schrieb Mike Hanby: >>>> >>>>> As far as I can tell, 'qtype INTERACTIVE' doesn't ever get used since >>>>> qrsh, qsh, qsub, qlogin are all treated as BATCH. >>>> >>>> Not by default. For `qlogin`, `qsh` and `qrsh` (w or w/o command) the >>>> default should route them to a queue of type "INTERACTIVE", while `qsub` >>>> is only running in queues of type "BATCH". >>>> >>>> But: >>>> >>>> "INTERACTIVE" should be read "IMMEDIATE" and the behavior can be changed >>>> with the option "-now y/n" to `qsub` (please have a look at `man qsub` for >>>> this option). >>>> >>>> Hence `qlogin -now n` will request a "BATCH" queue, while `qsub -now y >>>> ...` would demand an "INTERACTIVE" queue. >>> >>> I think I started to try to sort out that confusion in the man pages but >>> got distracted or confused. Would someone else like to have a go? >>> >>> As far as I remember, you can distinguish qlogin and command-less qrsh >>> with JSV if necessary. >> >> For the client side JSV yes, as the name of the command will be output for >> CLIENT. But not for the ones started by the qmaster (i.e. server side JSV) >> as the CMDNAME will be NONE in both cases and CONTEXT is "server"/CLIENT is >> "qmaster". You can't even decide between `qrsh` with command and `qsub` >> AFAICS. > > We currently distinguish between qrsh/qlogin and batch jobs in the > server side JSV by the presence of QRSH_PORT in the requested > environment. I believe the presence of this environment variable is > an undocumented feature and IIRC at least one of the forks was > proposing to get rid of it. Also if you are worried about abuse > someone could probably set QRSH_PORT by hand when submitting a qsub > command.
Nice catch :-) You could do some sanity checks, whether the set value is meaningful too. -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
