Kyle Stern <kstern422@...> writes: > > > > > > > > > > When I set a time limit for my salloc, why do I still have to exit from it once the allocation is revoked? For example: > > salloc -t1 > salloc: Granted job allocation 112645 > > salloc: Job 112645 has exceeded its time limit and its allocation has been revoked. > > ^C > > echo $SLURM_JOBID112645 > > exit > > echo $SLURM_JOBID> > I'm using v14.11.8. > > >
Hi Kyle, Maybe the following can help answer your question. Just my guess, I haven't tested this. >From the salloc man page, --time (-t) option: "When the time limit is reached, each task in each job step is sent SIGTERM followed by SIGKILL." Notice that it says "each task in each job step". Your shell that gets created as a result of your salloc command is not a task in a job step. If you used the method described in the FAQ to launch your shell then I would guess the salloc shell would also be terminated. See: http://slurm.schedmd.com/faq.html#salloc_default_command The man page for scancel might also help explain the difference in terminating a job step vs the batch command. Especially the "--batch" and "--signal" options and the whole "ARGUMENTS" section. Deric
