Skip to content
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.

Don't start the update process if one is already running #65

Open
nigredo-tori opened this issue Apr 8, 2020 · 1 comment
Open

Don't start the update process if one is already running #65

nigredo-tori opened this issue Apr 8, 2020 · 1 comment

Comments

@nigredo-tori
Copy link

As of now, the update process is started once every 15 minutes. If nvd.nist.gov slows down for some reason (I've seen dramatic slowdowns a couple days ago), we can have two or more update processes running concurrently. I suggest doing something like this instead:

flock -n /tmp/nvd.lock /mirror.sh

so that the spawned process immediately exits if there is another one running.

@nigredo-tori nigredo-tori changed the title Don't run an update process if one is already running Don't start the update process if one is already running Apr 8, 2020
@chris-gillatt
Copy link
Contributor

Just change it to once per hour? Every 15 minutes seems fairly aggressive - no wonder nvd.nist.gov is slowing down!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants