We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
So, there's this case when some modules create the same data on the logs and output folder. For example, waybackurls, gau, this has this problems:
In a recent scan I ended up with the following:
35 GB ../logs/* 35 GB ../output/* 35 GB outputfile.txt
I had to manually remove the logs and output folders but it failed in previous attempts because of lack of storage.
Solution
The text was updated successfully, but these errors were encountered:
Have you considered using the --rm-logs flag while scanning with Axiom? It might be usefull in addressing this issue
Sorry, something went wrong.
I have experienced this problem several times too ...
Doesn't help, because it will remove the logs after the scan, not during the scan.
gotcha! Yes, in my opinion this improvement would also be very useful
No branches or pull requests
So, there's this case when some modules create the same data on the logs and output folder. For example, waybackurls, gau, this has this problems:
In a recent scan I ended up with the following:
35 GB ../logs/*
35 GB ../output/*
35 GB outputfile.txt
I had to manually remove the logs and output folders but it failed in previous attempts because of lack of storage.
Solution
The text was updated successfully, but these errors were encountered: