purging old events
Posted: Fri Jan 28, 2005 1:49 pm
I've just started out using Zoneminder and have found it to be a great piece of software so far.
I intend to use ZM for documenting the progress of the construction of a building. The site is surrounded by a number of Axis network cameras.
There is a number of editors who will pick out the most interesting pieces recorded by ZM (videos and images) and save them off somewhere. The way I understand it, ZM's archive functionality can be used for this as well.
Those bits not archived should be aged out, much like logrotate does for logfiles that have exceeded a certain age.
I tried to accomplish this by using the default purgewhenfull filter and setting it to 90% of disk usage. Now that threshold has been reached and my ZM is in the progress of clearing all unarchived material... Not what I expected...
Now my question is this: Which is the best way to set up the filters so that I have a constant pool of unarchived (mos current) material in ZM while the already archived material is left untouched? The idea is for example to have only the last week of material in ZM. The editors can pick out their stuff during that period, if they come too late, it will have been deleted.
Any hints welcome!
I intend to use ZM for documenting the progress of the construction of a building. The site is surrounded by a number of Axis network cameras.
There is a number of editors who will pick out the most interesting pieces recorded by ZM (videos and images) and save them off somewhere. The way I understand it, ZM's archive functionality can be used for this as well.
Those bits not archived should be aged out, much like logrotate does for logfiles that have exceeded a certain age.
I tried to accomplish this by using the default purgewhenfull filter and setting it to 90% of disk usage. Now that threshold has been reached and my ZM is in the progress of clearing all unarchived material... Not what I expected...
Now my question is this: Which is the best way to set up the filters so that I have a constant pool of unarchived (mos current) material in ZM while the already archived material is left untouched? The idea is for example to have only the last week of material in ZM. The editors can pick out their stuff during that period, if they come too late, it will have been deleted.
Any hints welcome!