@@ -11,7 +11,7 @@ A resource request must specify a partition, an account, and other parameters su
```
sbatch script.sh
```
where `script.sh` is the job script.
where *script.sh* is the job script.
## Job script examples
...
...
@@ -60,7 +60,7 @@ Submit a job:
```
sbatch script.sh
```
Cancel the `job_id` job (`job_id` is the number provided by Slurm to identify the job):
Cancel the *job_id* job (*job_id* is the number provided by Slurm to identify the job):
```
scancel job_id
```
...
...
@@ -68,7 +68,7 @@ Display the jobs in the waiting queue:
```
squeue
```
Display the jobs of user `username` in the waiting queue:
Display the jobs of user *username* in the waiting queue:
```
squeue -u username
```
...
...
@@ -76,7 +76,7 @@ squeue -u username
## Job and cluster monitoring
In the output of the `squeue` command, the "ST" column provides the state of the job. The most common states are:
***R**: running.
***PD**: pending. The job is awaiting or resources.
***PD**: pending. The job is awaiting for resources.
***S**: suspended. This typically happens when the job is preempted by another job. In this case, no action is required. Slurm will resume the job when the preemptor job ends.
The title of the last column displayed by `squeue` is "NODELIST(REASON)":
...
...
@@ -102,7 +102,7 @@ The `sinfo` command displays the current state of compute nodes:
## Accounting
Slurm is connected to a database recording job acccounting data. The `sacct` and `sreport` commands allow to access this accounting information.
