[gridengine users] export of environment variables from start_proc_args
d.love at liverpool.ac.uk
Thu Jul 12 17:05:36 UTC 2012
Mark Dixon <m.c.dixon at leeds.ac.uk> writes:
> Things I think we've used starter_methods for in the past:
Gosh. You live in interesting times^Wclusters.
> * 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
Could you post the recipe/code? DMTCP is facing the knife for exactly
that, but C++ encourages displacement activities.
> * Allocating hardware (e.g. core binding in pre-6.2 versions, graphics hw)
How well does that work without scheduler support?
> * Firewall twiddling
Is that to control access to horrible licence servers, for instance, and
is it possible to do it per-process with iptables? (We've been somewhat
stymied by old stuff in RH5 and didn't pursue it.)
> * PE_HOSTFILE rewriting
> * 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
Yes, it just seems hard to do it correctly, particularly in shell, and
it's not privileged.
> Some of these require calling sudo scripts,
Yes, hooks need to be runnable with privileges.
> some have elaborate shell
> scripts setting environment variables.
More elaborate than
Community Grid Engine: http://arc.liv.ac.uk/SGE/
More information about the users