Ok, I think get what you are saying. It does say it won't suspend if PreemptParameters=reclaim_licenses is set. If you don't set that you could then suspend and catch the signal. Once that happens, you can do what you like with the licenses. I guess to answer your direct question, you CAN set PreemptMode to SUSPEND, it just won't work if you also set PreemptParameters=reclaim_licenses. Will that ever be implemented? Probably not, but maybe, if someone who is paying for support requests it. There would be quite a bit of details involved to make it work everywhere. If you are looking for a way to get to your apparent goal (suspend a job, but also free up the license it was using), you could cobble something together that does that. To get to a real solution, you would need to include all of the other pertinent requirements in your plan. It is, of course, possible with all requirements "You cain't get there from here" On 9/11/2026 12:36 AM, Peter via slurm-users wrote:
Catching the signal is not the issue. The issue is that I would like to use PreemptMode=SUSPEND, not REQUEUE or CANCEL. With SUSPEND, jobs are never actually suspended when they use licenses.