22-04-04 10:00
ZoneMinder 1.19.2 Released
By PHILIP COOMBES
ZoneMinder version 1.19.2 has been released today.
This release includes a number of minor enhancements to filter functionality aimed at making event filters more useful for event management in general. It also contains some minor fixes intended to address reported usability and vulnerability issues.
The changes in full are describe below (taken from the README) :-
o FEATURE – The default replay rate and live and event scale settings are now configurable on a per bandwidth basis rather than globally. This allows you to view at full scale when you have high bandwidth and at smaller scales when you do not have so much resource. You will need to re-configure your previous defaults as they will be lost.
o FEATURE – Filters can now include a specification of the preferred sort order of the results.
o FEATURE – Filters can now include a specification to limit the results to a predefined maximum
o FEATURE – Two new filter elements have been added. These are disk blocks and disk percentage. These are event independent and return the amount of disk space used on the event partition in terms of disk blocks or percentage as returned by df(1). Thus filters using these criteria will either match all events or none at all depending on the disk usage at the time of filter execution. The addition of these terms along with the ability to sort and limit filter results now means it is possible to create a filter that will automatically clear out old events once disk usage exceeds a certain value. Included in the database schemas for both new installations and upgrades is a sample filter called PurgeWhenFull which can be used to do this. It is initially not set to do anything automatically so if you want to use it, you should load it into the filter selection window, modify it to your taste and then save it, selecting ‘auto delete’. Please note that filters created using disk related terms to delete events should always contain a limit term also otherwise it is possible for all events to match and thus be deleted. Using a limit ensures that only a small number are affected at any one time.
o FEATURE – Filters can now be defined to automatically execute an external script or program of your choosing. This can be specified when the filter is saved. Note that for security reasons this cannot be just any arbitrary command but must be readable and executable by your web server effective user. The script or program you specify here will be executed in the events root directory once for each event and will be passed one parameter containing the relative path to the event directory. This will normally be of the form <MonitorName>/<EventId> so it it possible to determine both the monitor and event in question from the path. Note also that a flag is set per event as with other auto actions indicating that an executable script has been run on that event and so to exclude it from subsequent matches. However if you have several filters all with executable scripts you will find that only the first gets executed as the flag will be set following successful completion and so no further scripts will be run on that event. Successful completion is indicated by the script returning a zero exit status, any other status indicates an error and the executed flag will not be set.
o FIX – In some circumstances temporary diagnostic images were being saved instead of highlighted analysis images. This is now corrected.
o FIX – When viewing a list of frames in an event, the link to the diagnostic image was incorrect. This is now fixed.
o FIX – The Archive link from the monitor watch window has been fixed. Previously this generated a bogus window.
o FIX – The zone definition have been updated so that selecting the various types of zones etc only disables those options you no longer have access to rather than wiping them out entirely. This is also true of the zone when saved. Thus you can now more easily change a zone to be temporarily inactive for example and have your previous active settings restored in the future.
o FIX – Selecting an event from the list generated by a filter that included a Monitor Name term did not previously work properly. This is now fixed.
o FIX – A number of the constants used internally have been renamed to be more consistent. Hopefully nothing is broken!
o FIX – Following notification of a potential vulnerability in zms by Mark Cox, all non-trivial string and buffer copies are now limited by the maximum size of the destination. Mark has also asked me to include the following notice relating to this, which I am very happy to do. "This issue was discovered by Mark J Cox <mark@awe.com>. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2004-0227 to this issue."
o LANGUAGE – An additional Italian language translation has been added. One, by Davide Morelli, was included in 1.19.1 but not announced. However like buses another one has come along, from Tolmino Muccitelli, and so they are both now present. The original translation is accessible by selecting it_it as the language whereas the new one is it_it2. I would prefer if they were merged as two versions of one language is not easy to maintain when I don’t know what the differences mean!
o LANGUAGE – A version of Argentinian Spanish by Fernando Diaz has also been included and is accessible by setting your language to es_ar. As with all the language translations I cannot vouch for the completeness or accuracy of the language files so feel free to feedback any updates you think should be made.
o NOTE – None of the non-English language files in this release do not contain any translations of the new, or modified, tokens which have been introduced in this release. All new or modified tokens are included in the language files in English. There will shortly be a point release which includes these language updates assuming I can get translations of them in a reasonable timescale.
As usual, please visit the downloads area to get it, or view the README file.
|
