[gridengine users] export of environment variables from start_proc_args

[Reuti]

Am 10.07.2012 um 10:25 schrieb Mark Dixon:

> On Mon, 9 Jul 2012, Dave Love wrote:
> ...
>> You essentially need to mimic the built-in starter, which is why it's
>> best to hook into it instead.  The mimic is straightforward as long as
>> you don't use shell and can follow the built-in code.
>> 
>> What sort of things do people need to do other than firkle with
>> environment variables (and how elaborately for that?), considering a
>> starter hook stack ? la SLURM?
> 
> A starter hook stack sounds a great way do this.
> 
> Things I think we've used starter_methods for in the past:
> 
> * Setting OpenMP thread affinity variables
> * Setting sensible default variables / aliases (e.g. in case of no "-V")
> * Setting hardware or service-specific variables
> * Starting X servers
> * Transparent (from the job script's perspective) serial BLCR integration
> * Allocating hardware (e.g. core binding in pre-6.2 versions, graphics hw)
> * Firewall twiddling
> * PE_HOSTFILE rewriting

This I would suggest to do in the start_proc_args of the PE, but it might be personal taste of course.

-- Reuti


> * Extra logging
> * Kludging round GE bugs (e.g. setting the module function)
> 
> I found it a pretty good place to put things that extends gridengine functionality.
> 
> Some of these require calling sudo scripts, some have elaborate shell scripts setting environment variables.
> 
> Mark
> -- 
> -----------------------------------------------------------------
> Mark Dixon                       Email    : m.c.dixon at leeds.ac.uk
> HPC/Grid Systems Support         Tel (int): 35429
> Information Systems Services     Tel (ext): +44(0)113 343 5429
> University of Leeds, LS2 9JT, UK
> -----------------------------------------------------------------
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users