[FEATURE REQUEST] Ability to pause scan by sending a signal to process

[nil0x42]

Is your feature request related to a problem? Please describe. While using feroxbuster in an automated way, being able to pause it with SIGUSR1 or SIGHUP would be way more useful than ability to pause only from an attached tty.

[epi052]

hey there, thanks for the feedback! I have a few questions, but mostly to appease my curiosity. Please don't take them in a negative way, I'd just like to understand your workflow, as it's something that more than a few users do, but I don't, so would love your input.

• Is this part of an automated recon setup or similar?
• How often do you need to pause while scanning this way?
• If it's automated, what is the prompt/event that makes you want to pause?
• If it's part of an automated process, what does pausing allow you to do/fix/troubleshoot? I.e. why do you want to pause during your pipeline / how does it add value?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nil0x42]

I need to pause from signal is related to spreading requests by target.

For example, if i have 100 target sites, instead of scanning site1 for 10 hours, then site2, site3, etc... i prefer scanning each one for 1minute (for example), pausing, then resuming when all sites have been scanned for 1min. It can now be partially achieved with --threads. But ability to pause is a must have, because when the pipeline depends on server uptime, upstream proxy, possible bugs, etc, it's a pain.

Generally i prefer splitting all my jobs/pipelines into short time jobs, so i don't loose too much data when something goes wrong. I avoid as much as possible multi-day jobs