[GE users] identifing a parallel job

Reuti reuti at staff.uni-marburg.de
Thu Sep 4 11:33:29 BST 2008


Hi,

Am 04.09.2008 um 12:19 schrieb Davide Cittaro:

> On Sep 3, 2008, at 6:15 PM, Reuti wrote:
>>
>> you may base it on a $PE of course (see man qsub) whether it't  
>> unset, but somehow I would create a special queue for interactive  
>> jobs and test in the wrapper for "QUEUE=<your_login_queue>". You  
>> may also check the "JOB_SCRIPT=QRSH" (all for qrsh with command,  
>> otherwise a different entry in SGE's configuration is used anyway  
>> to get a shell to login.
>>
>> To get rid of the wrapper later on, it might be good to prefix the  
>> launch of it with "exec in.rsh.d $*" (don't overlook the necessary  
>> command line arguments) and avoid an additonal process.
>
>
> I'm trying with the dumbest script ever:
>
> #!/bin/bash
>
> the_command="/usr/sbin/sshd -i"
> if [ $PE ]
> then
> 	the_command=/usr/sbin/in.rshd
> fi
> exec $the_command $*
>
> and
>
> #!/bin/bash
>
> the_command=/usr/bin/ssh
> if [ $PE ]
> then
> 	the_command="$SGE_ROOT/bin/$SGE_ARCH/qrsh"

won't this end up in a loop, when "qrsh" is calling your wrapper again?

> fi
> exec $the_command $*
>
>
> qrsh jobs work, not qmake and lam_mpi batch ones... Which is the  
> default rsh_command  and rlogin_command in sge?

Please have a look here to change the settings and set it to any  
script you like:

http://gridengine.sunsource.net/howto/qrsh_qlogin_ssh.html

--Reuti

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list