ZoneMinder
/
zoneminder
mirror of https://github.com/ZoneMinder/zoneminder.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Added further comments to timestamp_on_capture option. 

git-svn-id: http://svn.zoneminder.com/svn/zm/trunk@865 e3e1d417-86f3-4887-817a-d78f3d33393f
pull/27/merge
stan 2004-02-18 15:36:22 +00:00
parent 8526aa69aa
commit 872b7188e0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
zmconfig.pl.in
View File

@ -273,7 +273,7 @@ my @options =
name => "ZM_TIMESTAMP_ON_CAPTURE",
default => "yes",
description => "Timestamp images as soon as they are captured",
help => "ZoneMinder can add a timestamp to images in two ways. The default method, when this option is set, is that each image is timestamped immediately when captured and so the image held in memory is marked right away. The second method does not timestamp the images until they are either saved as part of an event or accessed over the web. The timestamp used in both methods will contain the same time as this is preserved along with the image. The first method ensures that an image is timestamped regardless of any other circumstances but will result in all images being timestamped even those never saved or viewed. This may incur a very slight performance penalty.",
help => "ZoneMinder can add a timestamp to images in two ways. The default method, when this option is set, is that each image is timestamped immediately when captured and so the image held in memory is marked right away. The second method does not timestamp the images until they are either saved as part of an event or accessed over the web. The timestamp used in both methods will contain the same time as this is preserved along with the image. The first method ensures that an image is timestamped regardless of any other circumstances but will result in all images being timestamped even those never saved or viewed. The second method necessitates that saved images are copied before being saved otherwise two timestamps perhaps at different scales may be applied. This has the (perhaps) desirable side effect that the timestamp is always applied at the same resolution so an image that has scaling applied will still have a legible and correctly scaled timestamp.",
type => $types{boolean},
category => 'video',
},