... | ... | @@ -97,12 +97,12 @@ You can then start the interactive executions by using the srun command: |
|
|
|
|
|
$ srun [--other-options] ./code
|
|
|
|
|
|
*Comments* If you do not specify any option for the srun command, the options for `salloc` (for example, the number of tasks) will be used by default.
|
|
|
>Comments: if you do not specify any option for the srun command, the options for `salloc` (for example, the number of tasks) will be used by default.
|
|
|
|
|
|
**Important**
|
|
|
|
|
|
- After reserving resources with salloc, you are still connected on the front end (you can verify this with the hostname command). It is imperative to use the srun command so that your executions use the reserved resources.
|
|
|
- If you forget to cancel the reservation, the maximum allocation duration (by default or specified with the --time option) is applied and this amount of hours is then counted for the project you have specified. Therefore, in order to cancel the reservation, you must manually enter:
|
|
|
- After reserving resources with `salloc`, you are still connected on the front end (you can verify this with the `hostname` command). It is imperative to use the `srun` command so that your executions use the reserved resources.
|
|
|
- If you forget to cancel the reservation with `scancel`, the maximum allocation duration (by default or specified with the `--time` option) is applied and this amount of hours is then counted for the project you have specified. Therefore, in order to cancel the reservation, you must manually enter:
|
|
|
|
|
|
```
|
|
|
$ exit
|
... | ... | |