Am 12.05.2011 um 14:34 schrieb LaoTsao:
May be just use .sge_request for user and set -V for env variable
export and -v env=vale, set value
Or global setting sge_request
It seems that one can also use prolog for site or for user@ to set
some env for queue
No, the prolog won't inherit anything to the jobscript. And it won't
set anything for a particular user only, it will instead run the
prolog under a different user than the jobscript will run later on.
-- Reuti
Sent from my iPad
Hung-Sheng Tsao ( LaoTsao) Ph.D
On May 12, 2011, at 4:14 AM, "Esztermann, Ansgar" <[email protected]
> wrote:
On May 11, 2011, at 18:11 , Reuti wrote:
What about "adjusting" the file for the environment in the spool
directory of the job by start_proc_args? For each job there is a
directory on the master node of the parallel job and inside the to
be
changed file <exec_spool_dir>/<exechost>/active_jobs/
<job_id>.<task_id>/environment.
Thanks, I'll look into that.
To distribute it to the slave nodes the `qrsh -inherit -V` can do
it.
That's probably not even necessary -- the problem at hand is that
with OMP_NUM_THREADS unset, (some) jobs will grab an entire node
even if assigned just a few CPUs. However, our PEs are set up with
allocation_rules of $pe_slots or n (where n is the number of cores
on the node), so multi-node jobs never have to share any of their
nodes.
A.
--
Ansgar Esztermann
DV-Systemadministration
Max-Planck-Institut für biophysikalische Chemie, Abteilung 105
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
