Dear Reuti, The part of submitted script: #----start---- #$ -pe mpi4 8 #$ -l h="compute-0-27|compute-0-30" #$ -q all.q #$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1 #----end----
$ qconf -sp mpi4 pe_name mpi4 slots 9999 user_lists NONE xuser_lists NONE start_proc_args /opt/gridengine/mpi/startmpi.sh $pe_hostfile stop_proc_args /opt/gridengine/mpi/stopmpi.sh allocation_rule 4 control_slaves FALSE job_is_first_task TRUE urgency_slots min accounting_summary TRUE The master node is compute-0-27, while the slave node is compute-0-30. The variable "LD_PRELOAD" can only take effect on master node (compute-0-27). That is, the library shouldn't be loaded at slave node (compute-0-30). I know and I tested you said. Although the env_list: LD_PRELOAD=/home/wuy/bin/libtime.so.1, the library shouldn't be loaded at slave node (compute-0-30). Thanks! Yong WU 2013/12/4 Reuti <[email protected]> > Hi, > > Am 04.12.2013 um 11:31 schrieb Yong Wu: > > > I want to set a environment variable on slave nodes, and I did this in > my submitted script: > > #$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1 > > The variable will bet set at execution time of the script, wherever it's > executed. Due you mean: > > - the location is different for slave nodes in the cluster? > - the library shouldn't be loaded at all on slave nodes? > > Did you test with an: > > echo $LD_PRELOAD > > in the jobscript whether it's set? It will also be listed in `qstat -j > <job_id>`. > > -- Reuti > > > > But this variable can only take effect on master node. How to set a > environment variable on slave nodes? > > > > Any help about this issue will be apreciated! > > > > Thanks! > > > > Yong WU > > > > _______________________________________________ > > users mailing list > > [email protected] > > https://gridengine.org/mailman/listinfo/users > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
