Clean out old OSSEC diff and state files #7327
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These files are never pruned by OSSEC so they tend to accumulate, which can be a big deal for very big binary files like the ones in /boot. A script triggered by a daily timer will now clean up old state and diff files that are more than a year old. Fixes #7325.
legoktm
force-pushed
the
stg-cleanup-ossec
branch
from
0162450
to
9af9f43
Compare
|
(last push was a rebase) |
zenmonkeykstop
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
Ready for review
Description of Changes
These files are never pruned by OSSEC so they tend to accumulate, which can be a big deal for very big binary files like the ones in /boot.
A script triggered by a daily timer will now clean up old state and diff files that are more than a year old.
Fixes #7325.
Testing
How should the reviewer test this PR?
It is hard to test in a realistic scenario unless you have a long running instance with a lot of these files accumulated over the years. IMO the simulated testing should be sufficient for now and we can do more sophisticated testing with old instance snapshots later (once other changes have accumulated too).
Deployment
Any special considerations for deployment? n/a
Checklist