I would like to use Monitor to automatize some tasks : i’ve a config which aims to parse ip:port from a website and save them to a proxy file. I’ve created another config which uses this proxy file and a wordlist as well.
I would like each time CPM is very low, to stop the wordlist’s job, then start proxy grabbing job to update the proxy file, then restart the wordlist’s job with the refreshed proxy file.
My question is : when you start and retsart a same job, is proxy file reparsed from the begining, or do I need “reload proxy” task ?
When you start a job it automatically reloads proxies so there’s no need to put a manual reload there.
Maybe the thing that is missing here is the fact that you need to reset the skip to 0 otherwise the job will start with the wordlist at the previous position.
Do you need to stop a job to reload proxy with monitor’s task ? If I stop, “hint” will go down to 0, as wordlist is very huge, I won’t see clearly how many hints I’ve gained when I’ll finish the job (+ the fact I’ve still some bug in the DB despite what you suggested on Github) …
Ii dont think I can do what I would like to because
i) triggers are linked to the job so that you can’t use a trigger like to check if when another job is finished
ii) you can’t do action after a job has finished completing only
What I want to do is :
i) when time progress is = 5h for job #1, run job #2 (it downloads new list of proxies) and when it finishes only, reload proxies of job #1
ii) when job #2 has finished, reload proxies of job #3 as well.
I am planning to write an API to perform operations on an OB2 instance via HTTP calls, so you will be able to write a simple script to do exactly what you want. Please wait until the API is implemented.
