On 6/5/2012 6:23 PM, Ron Chen wrote:
Since you already have more than 1 PE already set up in your cluster, why not
just test this with your existing setup?
Just pretend that one of the PEs is your new "parallel" PE, and then add the PE
request into your own $HOME/.sge_request file.
http://gridscheduler.sourceforge.net/htmlman/htmlman5/sge_request.html
Qsub a test job using your own account, and run qstat to list the details of
the job.
When everything is good and users are happy, then do it properly by setting up
the real one PE and modify $SGE_ROOT/default/common/sge_request.
I bet you can do the first part in less than 5 mins, which is really quicker
than sending an email to the list and waiting for replies.
Hi Ron.
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 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
But as I thought, when I qsub the submit script, it errors with:
Unable to read script file because of error: ERROR! -pe option must have
range as 2nd argument
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).
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.
Joseph
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
