Difference between revisions of "PurgeWhenFull"
(Created page with "==About== PurgeWhenFull is a filter which deletes (default settings) 100 events when the DiskPercent is 90% full. ==Tuning== It's necessary to tune PurgeWhenFull, if you have...") |
|||
| Line 2: | Line 2: | ||
PurgeWhenFull is a filter which deletes (default settings) 100 events when the DiskPercent is 90% full. | PurgeWhenFull is a filter which deletes (default settings) 100 events when the DiskPercent is 90% full. | ||
== | ==Configuration== | ||
It's necessary to tune PurgeWhenFull, if you have a larger system, or you are creating a lot of events. | It's necessary to tune PurgeWhenFull, if you have a larger system, or you are creating a lot of events. | ||
Essentially, if you are making more than 100 events between the PurgeWhenFill commands you will | Essentially, if you are making more than 100 events between the PurgeWhenFill commands you will | ||
get a full HDD. Set it to 1000 and put the disk percent at 50% when starting a new system. | get a full HDD. Set it to 1000 and put the disk percent at 50% when starting a new system. Watch to make sure it | ||
doesn't go over 50%. | |||
==Cleaning up a 100% Full HDD== | ==Cleaning up a 100% Full HDD== | ||
Revision as of 20:00, 11 February 2017
About
PurgeWhenFull is a filter which deletes (default settings) 100 events when the DiskPercent is 90% full.
Configuration
It's necessary to tune PurgeWhenFull, if you have a larger system, or you are creating a lot of events. Essentially, if you are making more than 100 events between the PurgeWhenFill commands you will get a full HDD. Set it to 1000 and put the disk percent at 50% when starting a new system. Watch to make sure it doesn't go over 50%.
Cleaning up a 100% Full HDD
If you have gotten the disk space full, you will notice that all new events being created are given a time of 00:00. To clean this up:
- Run a filter manually, to delete 1000 events with less than 1 time. You can usually click the delete, then click the delete
again. It will not require you to go back to the filter screen each time.
then
- /usr/bin/zmaudit.pl
and clean up the items in the HDD that do not have corresponding events in the DB. If you've already filled the DB with 00:00 events.
- Finally check off OPT_FAST_DELETE in the config, so that when events are deleted, it instantly deletes the images, instead
of waiting for zmaudit.pl to cleanup later.
