![]() On modern systems, we recommend that you leave this off. ![]() ![]() If you do so, disk space will not be freed immediately so you will need to run zmaudit more frequently. If you are running on an older or under-powered system, you may want to set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later. When deleting events in the browser it can take a long time to remove all of this if you are trying to do a lot of events at once. Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT. Please consider the remaining tips in this answer to be ‘generally deprecated, use only if you must’. We no longer recommend use enable OPT_FAST_DELETE or RUN_AUDIT anymore, unless you are using an old or low powered system to run Zoneminder. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Optional slow delete: limit the number of results to a number, say 10 in the filter. “and” “archive status” equal to “unarchived only”. Optional skip archived events: click on the plus sign next to -7 days to add another condition. Save with ‘Run Filter In Background’ enabled to have it run automatically. ![]() You can also use a value of week or week and days: “-2 week” or “-2 week 4 day” To delete events that are older than 7 days, create a new filter with “End Date” set to “less than” and a value of “-7 days”, sort by “date/time” in “asc”ending order, then enable the checkbox “delete all matches”. You can duplicate the existing PurgeWhenFull filter by using Save As instead of Save.Ĭheck the zmfilter.log file to make sure it is running as sometimes missing perl modules mean that it never runs but people don’t always realize. If you have added other storage areas, you must create a PurgeWhenFull filter for each one, and specify the Storage Area as one of the parameters in the filter. Please note that that this filter will only affect the default storage location. The filter will immediately begin executing in the background to keep your disk within those limits. Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).Įnsure that the Run filter in background checkbox is checked.Įnsure that the Delete all matches checkbox is checked. Select ‘PurgeWhenFull’ and it will load that filter. In the filter window there is a drop down select box labeled ‘Use Filter’, that lets you select a saved filter. To enable it, go to Web Console, click on the word Filters in the UI header. So you may want to check if PurgeWhenFull is enabled and if not, enable it. If you already have an existing database and are upgrading ZoneMinder, it will retain the settings of the filter (which in earlier releases was disabled by default). Note that this filter is automatically enabled if you do a fresh install of ZoneMinder including creating a new database. The filter is called PurgeWhenFull and to find it, click on the word Filters in the header. Recent versions of ZoneMinder come with a filter you can use for this purpose already included. How can I stop ZoneMinder filling up my disk? ¶
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |