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

Added STRICT video config and note. 

git-svn-id: http://svn.zoneminder.com/svn/zm/trunk@366 e3e1d417-86f3-4887-817a-d78f3d33393f
pull/27/merge
stan 2003-01-24 15:25:38 +00:00
parent 7d30271e1f
commit 3368ebefd4
4 changed files with 33 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
README
View File

@ -744,8 +744,20 @@ Some things to check.
make sure that you have the correct settings. Use xawtv or something like that
to check for settings that work and then run zmu -d <device_no> -v to get the
settings. If you can't get them to work with that then the likelihood is they
won't work with ZM.
2. Web server. Ensure that your web server can serve PHP files. It's also
w on't work with ZM. Also check the system logs (usually /var/log/messages)
for any video configuration errors. If you get some and you're sure they're
not a problem then switch off ZM_STRICT_VIDEO_CONFIG in zmconfig.pl and
recompile and reinstall.
2. Start simple. Begin with a single monitor and single zone. You can run the
zmc capture daemon from the command line as 'zmc --device 0' (or whatever your
video device is). If it returns immediately there's a problem so check the
logs, if it stays up then your video configuration is probably ok. To get
more information out of it use debug as specified below. Also check that the
shared memory segment has been created by doing 'ipcs -m'. Finally beware of
doing tests as root and then trying to run as another user as some files may
not be accessible. If you're checking things as root make sure that you clean
up afterwards!
3. Web server. Ensure that your web server can serve PHP files. It's also
possible that your php.ini file may have some settings which break ZM, I'm not a
PHP guru but setting safe mode may prevent your PHP files from running certain
programs. You may have to set configuration to allow this. Also since the
@ -753,7 +765,7 @@ daemons are started by your web server, if it dies or is shut down then the
daemons may disappear. In this version the daemons are run under the control of
a script which should trap expected signals but it is possible this doesn't
cover all circumstances.
3. Use debug. ZM has various debug in it that by default will go into your
4. Use debug. ZM has various debug in it that by default will go into your
system log (via syslog). These will be of the form of
"Sep 14 14:50:11 localhost zma-0[1975]: INF [Front: 221000 - Processing at 4.26
fps ]"
@ -767,9 +779,7 @@ DLVL_zmc (or DLVL_zma etc) to a number between 0 and 9 will emit progressively
more debug though there's not a lot in there at present.
5. Paths. I admit it, the various paths in ZM are a bit of a nightmare. Make
sure that they are all correct and that permissions are such that the various
parts of ZM can actually run. Most of the places you need to specify this kind
of information are at the top of the associated configuration files but I've not
been able to get the automatic configure script to do all this by itself yet.
parts of ZM can actually run.
Also, if you are using IE under Windows and get lots of annoying clicks when
various windows refresh then you'll need to edit your registry and remove the
@ -833,6 +843,11 @@ options, I can't remember what it was but it's fixed!
- Retaint arguments in zmdc.pl - In some installations zmdc
was complaining about tainted arguments from the socket. These
are now detainted prior to sending and after receiving.
- Forced alarms - You can now force alarms when looking at the
monitor window should anything catch your attention. You have
to remember to switch them off as well though.
- Looser video configuration - Some video configuration errors
can now be ignore via the STRICT_VIDEO_CONFIG option.
Release 0.9.7 - Yes, a big jump in release number but a lot of changes too. Now
somewhat more mature, not really an alpha any more, and a lot of bugs fixed too.

6
src/zm.cpp
View File

@ -1369,7 +1369,7 @@ void Camera::Initialise( int device, int channel, int format, int width, int hei
if( ioctl( m_videohandle, VIDIOCSWIN, &vid_win ) )
{
Error(( "Failed to set window attributes: %s\n", strerror(errno) ));
exit(-1);
if ( !ZM_STRICT_VIDEO_CONFIG ) exit(-1);
}
struct video_picture vid_pic;
@ -1402,7 +1402,7 @@ void Camera::Initialise( int device, int channel, int format, int width, int hei
if( ioctl( m_videohandle, VIDIOCSPICT, &vid_pic ) )
{
Error(( "Failed to set picture attributes: %s\n", strerror(errno) ));
exit(-1);
if ( !ZM_STRICT_VIDEO_CONFIG ) exit(-1);
}
if(!ioctl(m_videohandle, VIDIOCGMBUF, &m_vmb))
{
@ -1454,7 +1454,7 @@ void Camera::Initialise( int device, int channel, int format, int width, int hei
if(ioctl(m_videohandle, VIDIOCSCHAN, &vid_src))
{
Error(( "Failed to set camera source %d: %s\n", channel, strerror(errno) ));
exit(-1);
if ( !ZM_STRICT_VIDEO_CONFIG ) exit(-1);
}
if( !ioctl( m_videohandle, VIDIOCGWIN, &vid_win))

2
src/zmcfg.h.z
View File

@ -33,3 +33,5 @@
#define ZM_FORCED_ALARM_SCORE <from zmconfig> // Score to give X10 forced alarms (from zmconfig)
#define ZM_RECORD_EVENT_STATS <from zmconfig> // Whether to record event statistical information, change to no if too slow (from zmconfig)
#define ZM_STRICT_VIDEO_CONFIG <from zmconfig> // Whether to allow errors in setting video config to be fatal

7
zmconfig.pl.in
View File

@ -302,6 +302,13 @@ my @options =
help => "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. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you 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 listing, and leaves the zmaudit daemon to clear up the rest later.",
type => $types{boolean},
},
{
name => "ZM_STRICT_VIDEO_CONFIG",
default => "yes",
description => "Whether to allow errors in setting video config to be fatal",
help => "With some video devices errors can be reported in setting the various video attributes when in fact the operation was successful. Switching this option off will still allow these errors to be reported but will not cause them to kill the video capture daemon. Note however that doing this will cause all errors to be ignored including those which are genuine and which may cause the video capture to not function correctly. Use this option with caution.",
type => $types{boolean},
},
{
name => "ZM_SHM_KEY",
default => "0x7a6d2000",