On Tue, Jun 5, 2012 at 11:20 PM, Joseph A. Farran <[email protected]> wrote: > Yeah, you have the advantage of knowing this product inside out and what is > difficult for us is simple, trivial and probably boring for you.
I guess he means that you can try some DIYs testing without damaging worrying too much... and see if something is possible first before actually modifying a production cluster. > I did edit my global "sge_request" and I entered: > > -pe make > > To hopefully make "make" my default pe name. Then in my OGE submit script, > I say: > > #$ -pe 64 This won't work, as the qsub command line parsing code always requires a PE name for -pe. > So it's the syntax which is difficult for us OGE beginners. I am trying > to have OGE choose a default pe name, but *NOT* the number of cores (slots). Without modifying Grid Engine, you can use a JSV or a qsub wrapper. Unless *every single job* in your cluster is a parallel job, adding "-pe" in the default request file is likely not something you want. > My goal is to be able to have a default Parallel Environment users get if > they don't choose one. They do of course have to pick the number of cores > (slots) since there is no real default for that. So really how many PEs you have in your cluster?? If I were to do it for your cluster, most likely I will add a client side JSV, and put -jsv in $SGE_ROOT/$SGE_CELL/common/sge_request . http://gridscheduler.sourceforge.net/htmlman/htmlman1/jsv.html In the client-side JSV, if it finds that the job is requesting to run in parallel, but there is no PE name specified, then it would then add the default PE name. Rayson > > Joseph > > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
