On Thursday, 17 October 2019, at 16:50:29 (+),
Goetz, Patrick G wrote:
> Are applications even aware when they've been hit by a SIGSTP? This
> idea of a license being released under these circumstances just
> seems very unlikely.
No, which is why SIGSTOP cannot be caught. The action is carr
Are applications even aware when they've been hit by a SIGSTP? This
idea of a license being released under these circumstances just seems
very unlikely.
On 10/15/19 1:57 PM, Brian Andrus wrote:
> It seems that there are some details that would need addressed.
>
> A suspend signal is nothing mo
tun Peksel*
oytun.pek...@semcon.com <mailto:oytun.pek...@semcon.com>
+46739205917
*From:*slurm-users *On Behalf
Of *Brian Andrus
*Sent:* den 15 oktober 2019 20:58
*To:* slurm-users@lists.schedmd.com
*Subject:* Re: [slurm-users] Execute scripts on suspen
ytun.pek...@semcon.com>
+46739205917
From: slurm-users On Behalf Of Brian
Andrus
Sent: den 15 oktober 2019 20:58
To: slurm-users@lists.schedmd.com
Subject: Re: [slurm-users] Execute scripts on suspend and cancel
It seems that there are some details that would need addressed.
A suspend signal
It seems that there are some details that would need addressed.
A suspend signal is nothing more than sending a SIGSTP (like hitting
ctrl-s), so the application is still in memory awaiting SIGCONT
So what should happen when it continues and there are no more licenses?
So the proper place for
It is quite weird if slurm has no mechanism as described. I have been digging
more into it and someone suggested a workaround using mail notifications. You
use a script instead of the mail application and catch the event then use use
sacct to see what is happening.
Two problems with this:
*
