Skip to content

Commit 4def96c

Browse files
authored
add how to doc on running multiple copies of cve-bin-tool (#904)
1 parent bb1d055 commit 4def96c

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

doc/multiple_scans_at_once.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# Best practices for running multiple scans at once
2+
3+
If you're running multiple instances of cve-bin-tool at once, you could
4+
potentially cause a race condition where multiple processes are trying
5+
to update the database from nvd at the same time. This is not ideal.
6+
7+
To avoid this, you should use a single command to run the nvd update, then turn off the updater in all other copies.
8+
9+
## Step 1: Update
10+
To update (without scanning) you can use the following command:
11+
12+
```
13+
cve-bin-tool -u now
14+
```
15+
16+
We recommend once per day, but this can be more frequently or less frequently depending on your needs. Ideally, you want to be sure this completes before you kick off any other scans, so that you aren't checking against a partial database.
17+
18+
## Step 2: Scan
19+
20+
Each parallel instance of cve-bin-tool can then be invoked as follows:
21+
22+
```
23+
cve-bin-tool -u never $path_to_directory_or_file
24+
```
25+
26+
27+
28+
29+
30+

0 commit comments

Comments
 (0)