Am 13.12.2011 um 17:19 schrieb Christoph Müller:

> Hi Reuti,
> 
> thanks for your quick response.
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Reuti [mailto:[email protected]]
>> Gesendet: Dienstag, 13. Dezember 2011 17:01
>> An: Christoph Müller
>> Cc: [email protected]
>> Betreff: Re: AW: [gridengine users] Access complex resources from prolog
>> script
> 
> 
>>> but I need to change all nodes in a different way. I do not have any file
>> access problems, the problem is the context/the SGE envvars, which are not
>> available in my SSH session.
>> 
>> Mhh - I'm still puzzeled at what point you need the ssh. To start the slaves 
>> of
>> the parallel job? To change the environment file on the slave nodes? If you
> 
> Yes. What I want to do is compute an environment variable (based on the 
> complex resource requested by the user and the resources of this type 
> available on each machine) and set this for the job. To do so, I want to SSH 
> to every node and adjust the environment file.

The problem is, that it's only created when `qrsh -inherit ...` is executed. 
There is nothing on the slave node beforehand - just an empty directory AFAICS. 
Also no environment file.

Why not putting it in a starter_method. Initialy I wasn't aware that it's a 
parallel job. What information you want to set up - a local scratch directory?


>> setup SGE's configuration to use ssh (in case you really need it), all 
>> variables
>> should be inherited from the sge_shepherd.
> 
> You mean that any SSH session I open from the prolog should inherit the 
> environment? That is not the case here. Where can I change the configuration 
> accordingly? What I can confirm is that the MPI jobs correctly inherit the 
> environment.

You defined ssh to be used in `qconf -sconf`? For a tight integration the PAM 
needs also to be adjusted.

http://arc.liv.ac.uk/SGE/htmlman/htmlman5/remote_startup.html

-- Reuti
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to