start:working_on_mogon:io_odds_and_ends:slurm_localscratch

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
start:working_on_mogon:io_odds_and_ends:slurm_localscratch [2021/06/10 17:27]
meesters
start:working_on_mogon:io_odds_and_ends:slurm_localscratch [2022/06/20 18:05]
meesters [Signalling in SLURM -- difference between signalling submission scripts and applications] - minor grammar fixes and removed doubled lines
Line 91: Line 91:
 $ sbatch --signal=SIGUSR2@600 ... $ sbatch --signal=SIGUSR2@600 ...
 </code> </code>
-This would send the signal ''SIGUSR2'' to the application ten minutes before hitting the walltime of the job. Note that the slurm documentation states that there is uncertainty of up to 1 minute.+This would send the signal ''SIGUSR2'' to the application ten minutes before hitting the walltime of the job. Note that the slurm documentation states that there is an uncertainty of up to 1 minute.
  
 **Usually** this requires you to use  **Usually** this requires you to use 
Line 99: Line 99:
 </code> </code>
  
-or rather +within a submission script to signal the batch-job (instead of all the children of but not the batch job itselft). The reason is: If using a submission script like the one above, you trap the signal within the script, not the application. 
- +
-<code bash> +
-#SBATCH --signal=B:SIGUSR2@600 ... +
-</code> +
- +
-withing a submission script to signal the batch-job (instead of all the children of but not the batch job itselft). The reason is: If using a submission script like the one above, you trap the signal within the script, not the application. +
  
 </callout> </callout>
  • start/working_on_mogon/io_odds_and_ends/slurm_localscratch.txt
  • Last modified: 2022/06/20 18:05
  • by meesters