Skip to content

Commit 574acf1

Browse files
committed
final tweaks
1 parent 1626b34 commit 574acf1

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

_posts/hpc/2019-02-05-smanage.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ smanage <strong>manage</strong>s jobs running on a
2727
## What do I need this for?
2828

2929
After you launch a bunch of jobs, it's hard to keep track of them. How many completed? How many crashed
30-
and failued in a horrific ending of memory exceed exceptions? In a nutshell, smanage enables you to submit and track large batches of jobs beyond the MaxArraySize limit set by slurm.
30+
and failed in a horrific ending of memory exceed exceptions? In a nutshell, smanage enables you to submit and track large batches of jobs beyond the MaxArraySize limit set by slurm.
3131

3232

3333
## What is a job array?
@@ -94,15 +94,17 @@ This is the goal of smanage. Now that you understand, let's briefly look at usag
9494
For more detailed examples, see the [smanage repository](https://www.github.com/esurface/smanage).
9595
If you want to learn more about Job arrays, check out this [AskCI post](https://ask.cyberinfrastructure.org/t/what-are-good-uses-for-job-arrays/733/3).
9696

97-
# Usage
9897

99-
## Local
10098

101-
For local usage, you can install the script by adding an alias to the program. First, wget it.
99+
## Usage
100+
101+
You can install the script by adding an alias to the program. First, wget it.
102102

103103
```bash
104+
104105
wget https://raw.githubusercontent.com/esurface/smanage/master/smanage.sh
105106
chmod u+x smanage.sh # makes it executable
107+
106108
```
107109

108110
Run the following line of code or copy it into the file '~/.bashrc' to make it permanent:
@@ -141,10 +143,10 @@ sbatch sleepy.sbatch
141143

142144
and then use it to learn about the different commands for smanage below.
143145

144-
## Report Mode (default): smanage report
146+
## Report Mode (default)
145147

146148
The reporting mode gives you a summary of your jobs. Here is what we see after
147-
launching sleepy.sbatch above.
149+
launching sleepy.sbatch
148150

149151
```bash
150152
[vsochat@sh-ln06 login /scratch/users/vsochat/sleepy]$ smanage report
@@ -158,7 +160,7 @@ Found jobs: 35512888
158160

159161
2 jobs with untracked status
160162
```
161-
We could have also used squeue:
163+
We could have also used old school squeue:
162164

163165
```bash
164166
[vsochat@sh-ln06 login /scratch/users/vsochat/sleepy]$ squeue -u vsochat
@@ -183,7 +185,7 @@ Found 1016 jobs: 36094475,36123253,36160821,36160826,36160831,36160945,36160947,
183185
Now we can try the command and look specifically for our "sleepy-job" by name.
184186
Let's run the command again, so we get two sets of sleepy jobs.
185187

186-
```
188+
```bash
187189
$ sbatch sleepy.job
188190
$ smanage report --sacct --name=sleepy-job
189191
Finding jobs using: /usr/bin/sacct -XP --noheader --name=sleepy-job

0 commit comments

Comments
 (0)