> On Aug 28, 2018, at 6:13 PM, Christopher Samuel wrote:
>
> On 29/08/18 09:10, Priedhorsky, Reid wrote:
>
>> This is surprising to me, as my interpretation is that the first run
>> should allocate only one CPU, leaving 35 for the second srun, which
>> also only n
> On Aug 28, 2018, at 6:35 AM, Chris Samuel wrote:
>
> On Tuesday, 28 August 2018 10:21:45 AM AEST Chris Samuel wrote:
>
>> That won't happen on a well configured Slurm system as it is Slurm's role to
>> clear up any processes from that job left around once that job exits.
>
> Sorry Reid, for
Folks,
I am trying to figure out how to advise users on starting worker daemons in
their allocations using srun. That is, I want to be able to run “srun foo”,
where foo starts some child process and then exits, and the child process(es)
persist and wait for work.
Use cases for this include Apa
