Hi,
the right API to use is the one that works. :-)
slurm_terminate_job() is an obsolete call and will be removed in the
next release. slurm_kill_job() is the one to use.
On 01/28/2014 03:30 PM, Michael Gutteridge wrote:
I'm writing a small tool using the api- I'm running into a segmentation
fault when I use "slurm_terminate_job" to remove a job from a node. It
seems to work properly if I use "slurm_kill_job":
ec = slurm_terminate_job( job_buf_ptr->job_array[j].job_id );
results in segfault
ec = slurm_kill_job( job_buf_ptr->job_array[j].job_id, 9, 0 );
works fine.
I'm having troubles generating the debug symbols I need from libslurm,
so I don't have a whole lot of good debugging information yet (will
provide soonest). Meantime- is there a generally preferred way to end a
running job via the API? It looks like terminate is neater (or at least
more thorough), but kill is getting the job done. Is there a reason
that "slurm_kill_job" shouldn't be used?
Thanks
Michael
--
Thanks,
/David/Bigagli
www.schedmd.com
