On 19 September 2012 17:38, Dave Love <[email protected]> wrote: > William Hay <[email protected]> writes: > >>>> 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. > > It sounds as if a bug report is called for. Could someone who knows > what seems to be missing there put it in the tracker? > >> 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 > > Isn't the port info crucial to making the comms work? > A little more effort and I think this https://arc.liv.ac.uk/trac/SGE/ticket/28 is what I was thinking of.
Never tried setting QRSH_PORT when submitting via qsub so can't say what happens then. Given our local policies there isn't much incentive for anyone to try this as you wouldn't gain anything that couldn't be got with qrsh command. William _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
