AW: AW: [GE users] Export Env Variables

reuti reuti at staff.uni-marburg.de
Fri Sep 18 16:52:42 BST 2009


    [ The following text is in the "utf-8" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Am 18.09.2009 um 17:40 schrieb carsten:

> I tried the following calls:
>
> exec "$@"
>
> exec "$*"
>
> exec $SGE_STARTER_SHELL_PATH "$*"
>
> exec $SGE_STARTER_SHELL_PATH "$@"
>
>
>
> All of them did not work. The application starts, but the setup of  
> the MPI universe timed out.

Which MPI?

-- Reuti


> Other MPI implementations have no problems, but this is the only PE  
> we have that uses catch_rsh. Setting the starter_method back to  
> NONE, the application works well.
>
> -- Carsten
>
>
> -----Ursprüngliche Nachricht-----
> Von: reuti [mailto:reuti at staff.uni-marburg.de]
> Gesendet: Freitag, 18. September 2009 16:13
> An: users at gridengine.sunsource.net
> Betreff: Re: AW: [GE users] Export Env Variables
>
> Am 18.09.2009 um 15:42 schrieb carsten:
>
>> Replacing the starter_method seems to be the only way.
>>
>> The problem is, that a simple replacement with 'exec "$@" ' crashes
>> a PE that use catch_rsh (was the case in 6u10, have not tested with
>> a 6.2 version yet).
>
> AFAIK the starter_method is (and was) never used for the PE scripts.
> Only for the jobscript.
>
> It will be applied for the slave tasks though, but this shouldn't be
> a problem. Maybe it depends on the kind of parallel lib. E.g. with
> MPICH(1) I see no problem.
>
> Did you use "$*" instead?
>
> -- Reuti
>
>
>> Regards,
>> Carsten
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: reuti [mailto:reuti at staff.uni-marburg.de]
>> Gesendet: Freitag, 18. September 2009 15:01
>> An: users at gridengine.sunsource.net
>> Betreff: Re: [GE users] Export Env Variables
>>
>> Am 18.09.2009 um 14:42 schrieb matbradford:
>>
>>> Is it possible to export environment variables from the PE start
>>> script so that they are accessible by the job.
>>>
>> No.
>>> We have an OpenMPI job and are currently using linux modules to
>>> load the environment correctly .
>>>
>>> At the moment this is in the actual job submission script, but we
>>> would prefer to move it to the PE start up script.
>>>
>>> I?ve had a quick play, and it doesn?t seem to matter what I do, I
>>> can?t create an environment variable of any sort in the PE start
>>> script and then access it from within the job.
>>>
>>> Any thoughts would be much appreciated.
>>>
>>
>> You can user a starter_method in the definition of the queue and then
>> exec the program:
>>
>> #!/bin/sh
>> export blabla=fubar
>> exec "$@"
>>
>> -- Reuti
>>
>>> Cheers,
>>>
>>> Mat
>>>
>>> Matthew Bradford
>>>
>>> Information Specialist
>>>
>>> Applications Services Field Operations EMEA
>>>
>>> UKIMEA RABU
>>>
>>> EDS, an HP company
>>>
>>> EDS c/o Rolls-Royce Plc, Moor Lane
>>>
>>> PO Box 31
>>> Derby
>>>
>>> DE24 8BJ
>>>
>>> email:  matthew.bradford at eds.com
>>>
>>> Office: +44 01332 632599
>>>
>>> Electronic Data Systems Ltd
>>> Registered Office: Cain Road, Bracknell, Berkshire, RG12 1HN
>>>
>>> Registered in England no: 53419
>>> VAT number: 432 99 5915
>>>
>>>
>>> We deliver on our commitments
>>>
>>> so you can deliver on yours.
>>>
>>>
>>>
>>> This message contains information which may be confidential and
>>> privileged. Unless you are the intended addressee (or authorised to
>>> receive for the addressee) you may not use, copy or disclose to
>>> anyone the message or any information contained in this message. If
>>> you have received this message in error, please advise the sender
>>> by reply email and delete the message.
>>> ? 2005 Electronic Data Systems Corporation. All rights reserved.
>>>
>>> Electronic Data Systems Ltd
>>>
>>> Registered Office:, Lansdowne House, Berkeley Square, London  W1J  
>>> 6ER
>>>
>>> Registered in England no: 53419
>>>
>>> VAT number: 432 99 5915
>>>
>>>
>>>
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do?
>> dsForumId=38&dsMessageId=217791
>>
>> To unsubscribe from this discussion, e-mail: [users-
>> unsubscribe at gridengine.sunsource.net].
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do?
>> dsForumId=38&dsMessageId=217796
>>
>> To unsubscribe from this discussion, e-mail: [users-
>> unsubscribe at gridengine.sunsource.net].
>>
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=217802
>
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe at gridengine.sunsource.net].
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=217810
>
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe at gridengine.sunsource.net].
>

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=217811

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list