Differences

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

--- public:usage:fuchs [2020/02/06 12:34] – [Per-User Resource Limits] geier
+++ public:usage:fuchs [2020/05/15 10:50] – [Job Monitoring] geier
@@ Line 150: / Line 150: @@
 ) For SLURM, a CPU core (a CPU thread, to be more precise) is a CPU.\\
-) Prevent the job from being requeued after node failure.\\
+) Prevent the job from being requeued after a failure.\\
 ) Send an e-mail if sth. goes wrong.\\
 ) Run job without Hyper-Threading.\\
@@ Line 164: / Line 164: @@
 on the command line. The job's output streams (''stdout'' and ''stderr'') will be joined and saved to ''slurm-ID.out'', where ''ID'' is a SLURM job ID, which is assigned automatically. You can change this behavior by adding an ''%%--%%output'' and/or ''%%--%%error'' argument to the SLURM options.
-For job monitoring (to check the current state of your jobs) you can use the ''squeue'' command. Depending on the current cluster utilization (and other factors), your job(s) may take a while to start.
+==== Job Monitoring ====
+For job monitoring (to check the current state of your jobs) you can use the ''squeue'' command. Depending on the current cluster utilization (and other factors), your job(s) may take a while to start. You can check the current queuing times by running ''sqtimes'' on the command line.
 If you need to cancel a job, you can use the ''scancel'' command (please see the ''manpage'', ''man scancel'', for further details).