Skip to content
Snippets Groups Projects
Commit 3a73f266 authored by Danny Auble's avatar Danny Auble
Browse files

BGQ - minor fix for --launch-cmd to print runjob instead of srun

parent 3419a62c
No related branches found
No related tags found
No related merge requests found
...@@ -320,10 +320,10 @@ extern int launch_p_setup_srun_opt(char **rest) ...@@ -320,10 +320,10 @@ extern int launch_p_setup_srun_opt(char **rest)
if (!opt.test_only) { if (!opt.test_only) {
int i = 0; int i = 0;
/* First arg has to be something when sending it to the /* First arg has to be something when sending it to the
runjob api. This can be anything, srun seemed most runjob api. This can be anything, we put runjob
logical, but it doesn't matter. here so --launch-cmd looks nice :), but it doesn't matter.
*/ */
opt.argv[i++] = xstrdup("srun"); opt.argv[i++] = xstrdup("runjob");
/* srun launches tasks using runjob API. Slurmd is not used */ /* srun launches tasks using runjob API. Slurmd is not used */
/* We are always going to set ntasks_per_node and ntasks */ /* We are always going to set ntasks_per_node and ntasks */
// if (opt.ntasks_per_node != NO_VAL) { // if (opt.ntasks_per_node != NO_VAL) {
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment