Hi, Am 26.03.2013 um 12:17 schrieb Arnau Bria:
> I'm migrating a bash jsv script to perl and adding some > modifications, but I have some doubts: > > 1) jsv_correct vs jsv_accept. From man: > > If the result_type is ACCEPTED the job will be accepted as it was > initially submitted by the end user. All param_commands and > env_commands which might have been sent before the > result_command are ignored in this case. The result_type CORRECT > indicates that the job should be accepted after all modifications sent > via param_commands and env_commands are applied to the job > > But if I do modifications (I'm doing jsv_sub_add_param) and then > jsv_accept, the job is modified and submited, so, why is jsv_correct > needed? what could happen if I do not correct but accept? I would say it's a bug, that the changes made to the job are committed. They should be ignored. > 2) core binding. I have it configured for serial and smp jobs, but > which is the correct strategy and configuration for mpi jobs? > Is linear going to span jobs acros different host sockets? AFAICS the request is applied on all machines which you get granted for the job. I.e. applied per `qrsh -inherit ...` besides setting it for the jobscript already. This is hard to handle in case of a round robin allocation, as you don't know in advance whether you get just one slot per machine or more. Maybe the best would be to use it with a fixed allocation rule only. -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
