-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
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
Add Ability To Customize Paths Scanned In Cron.daily #197
Comments
I would like to add it would be nice to be able to control the prune time for the cron.daily. Some of us would like to save quarantine/session/tmp data longer than 7 days. |
Isn't this already possible in 1.5 by using |
No these are currently hardcoded. |
I like the suggestion from @vwesisolak (although it doesn't look like it made it into 1.6), but I just meant to point out that you can currently add an additional scan via |
….daily pruning max age of quarantine/sess/tmp data issue #197
This has been pushed in latest commit as a conf.maldet option. You can also redefine any conf.maldet option explicitly for the cron execution by creating "[New] added conf.maldet option cron_prune_days for configuration cron.daily pruning max age of quarantine/sess/tmp data; issue #197" |
This was closed but looks like my initial suggestion for custom path handling (or similar) wasn't implemented. Any particular reason this change was rejected? Due to the notification requirements, performing multiple scans is not very helpful (I have a separate cron to send the last scan's output regardless of result). |
Hello,
Recently I wanted to modify the paths scanned in the daily cron but was unable to find a way to to this that would survive an update since the cron is replaced.
I propose adding handling so that
$custom_scan_paths
could be specified in$cron_custom_conf
or elsewhere and augment the detected paths to be scanned and/or override them with$override_scan_paths
.--Eric
The text was updated successfully, but these errors were encountered: