ZoneMinder Wiki - User contributions [en]

Axis

2011-10-23T08:03:37Z

Tijuca: /* AXIS M1114 */ fixing wrong entrys

[[Image:Axis cameras.jpg]]

ZoneMinder will work well with just about any [http://www.axis.com Axis camera], including the 205, 206, 207, 209, 210, 211 and M10 ranges. It will also work with the 213 and 2130 cameras and support their [[PTZ]] functions through the web interface.

Please note that early 207's has some hardware issues. See [http://www.zoneminder.com/forums/viewtopic.php?t=5022 this thread] in the forum for details.
Also note that the [http://www.axis.com/techsup/cam_servers/cam_2100/index.htm 2100 has been discontinued by Axis] and no longer supported, possibly due to hardware related problems. It's noted in the [http://www.zoneminder.com/forums/viewtopic.php?t=10079 forums that the camera sends the pictures it captures somewhat diced up.]

How to Offload the Motion to cameras [[AxisMotionDetection]]

== AXIS 2110 ==

/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS 207W ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS P33XX-V/VE ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240
or
<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS P1311 ==

<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS 213PTZ ==
The axis 213PTZ works perfectly. Use the folowing settings:
'''SOURCE'''
Remote Protocol: RTSP
Remote Method: RTP/RTSP
Remote Host Name: <USER>:<PASS>@<CAM IP/HOSTNAME>
Remote Host Port: 554
Remote Host Path: /mpeg4/media.amp

'''CONTROL'''
Controllable: Yes
Control Type: Axis API v2
Control Address: <USER>:<PASS>@<CAM IP/HOSTNAME>

The resolution must match the one especified in the camera settings. Resolutions up to CIF will work without any problems but 2CIF and 4CIF will need the shared memory tweak (lean more at the [[FAQ]])

The [[AxisMotionDetection]] trick works quite well with this camera.

The Max FPS option of zoneminder introduces very big latency, so I use the option of the camera for limiting the FPS.

This was tested with zoneminder 1.24.2 running on Gentoo stable

== AXIS M1031-W ==

[http://www.axis.com/products/cam_m1031w/ M1031-W]

'''SOURCE'''
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <CAM IP/HOSTNAME>
Remote Host Port: <CAM PORT>
Remote Host Path: /axis-cgi/mjpg/video.cgi?resolution=640x480

OR for mpeg-4

'''SOURCE'''
Remote Protocol: RTSP
Remote Method: RTP/RTSP/HTTP
Remote Host Name: <USER>:<PASS>@<CAM IP/HOSTNAME>
Remote Host Port: <CAM PORT>
Remote Host Path: /mpeg4/media.amp

[[Category:Cameras]]

== AXIS M1054 ==

Working just fine with my zoneminder setup under Ubuntu 10.04 and 11.04, using MJPEG setup.

My camera setup:
* Source type: remote
* Function: modect
* maximum fps 8.00
* alarm fps 30.00
* remote protocol: http
* remote method: simple
* remote host name: the DNS name of the camera (or IP adress I suppose)
* remote host port: 80
* remote host path: /axis-cgi/mjpg/video.cgi
* capture width: 1280
* capture height: 800

I just captured some thiefs with this setup, police caught them and used the pictures as proof. High quality pictures for that price of a camera and very reliable (running 1/2 year now without a single crash or disfunction).[http://www.blognesian.com/ ]

==AXIS M1114==
works with following entrys
* Source type: remote
* Function: [what_you_want]
* maximum fps 0 # don't put any value here
* alarm fps 0 # don't put any value here
* remote protocol: http
* remote method: simple
* remote host name: user:password@IP-Address or user:password@DNS_Name
* remote host port: 80
* remote host path: /mjpg/video.mjpg?resolution=480x360
* capture width: 480 #depends on your "remote host path" setting, must to be the same!
* capture height: 360 #depends on your "remote host path" setting, must to be the same!

Axis

2011-10-02T10:15:08Z

Tijuca: /* AXIS M1114 */ adding AXIS M1114

[[Image:Axis cameras.jpg]]

ZoneMinder will work well with just about any [http://www.axis.com Axis camera], including the 205, 206, 207, 209, 210, 211 and M10 ranges. It will also work with the 213 and 2130 cameras and support their [[PTZ]] functions through the web interface.

Please note that early 207's has some hardware issues. See [http://www.zoneminder.com/forums/viewtopic.php?t=5022 this thread] in the forum for details.
Also note that the [http://www.axis.com/techsup/cam_servers/cam_2100/index.htm 2100 has been discontinued by Axis] and no longer supported, possibly due to hardware related problems. It's noted in the [http://www.zoneminder.com/forums/viewtopic.php?t=10079 forums that the camera sends the pictures it captures somewhat diced up.]

How to Offload the Motion to cameras [[AxisMotionDetection]]

== AXIS 2110 ==

/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS 207W ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240

== AXIS P33XX-V/VE ==

<User>:<Password>@<IP Address>/axis-cgi/mjpg/video.cgi?camera=&resolution=320×240
or
<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS P1311 ==

<User>:<Password>@<IP Address>/mjpg/video.mjpg

== AXIS 213PTZ ==
The axis 213PTZ works perfectly. Use the folowing settings:
'''SOURCE'''
Remote Protocol: RTSP
Remote Method: RTP/RTSP
Remote Host Name: <USER>:<PASS>@<CAM IP/HOSTNAME>
Remote Host Port: 554
Remote Host Path: /mpeg4/media.amp

'''CONTROL'''
Controllable: Yes
Control Type: Axis API v2
Control Address: <USER>:<PASS>@<CAM IP/HOSTNAME>

The resolution must match the one especified in the camera settings. Resolutions up to CIF will work without any problems but 2CIF and 4CIF will need the shared memory tweak (lean more at the [[FAQ]])

The [[AxisMotionDetection]] trick works quite well with this camera.

The Max FPS option of zoneminder introduces very big latency, so I use the option of the camera for limiting the FPS.

This was tested with zoneminder 1.24.2 running on Gentoo stable

== AXIS M1031-W ==

[http://www.axis.com/products/cam_m1031w/ M1031-W]

'''SOURCE'''
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <CAM IP/HOSTNAME>
Remote Host Port: <CAM PORT>
Remote Host Path: /axis-cgi/mjpg/video.cgi?resolution=640x480

[[Category:Cameras]]

== AXIS M1054 ==

Working just fine with my zoneminder setup under Ubuntu 10.04 and 11.04, using MJPEG setup.

My camera setup:
* Source type: remote
* Function: modect
* maximum fps 8.00
* alarm fps 30.00
* remote protocol: http
* remote method: simple
* remote host name: the DNS name of the camera (or IP adress I suppose)
* remote host port: 80
* remote host path: /axis-cgi/mjpg/video.cgi
* capture width: 1280
* capture height: 800

I just captured some thiefs with this setup, police caught them and used the pictures as proof. High quality pictures for that price of a camera and very reliable (running 1/2 year now without a single crash or disfunction).[http://www.blognesian.com/ ]

==AXIS M1114==
works with following entrys
* Source type: remote
* Function: [what_you_want]
* maximum fps 8.00 # for example
* alarm fps 20.00
* remote protocol: http
* remote method: simple
* remote host name: user:password@IP-Address or user:password@DNS_Name
* remote host port: 80
* remote host path: /axis-cgi/jpg/image.cgi
* capture width: 1280 #depends on your camera settings, must to be the same!
* capture height: 800 #depends on your camera settings, must to be the same!

How to install and configure Postfix as a Gmail SMTP relay for ZoneMinder email filter events.

2011-08-07T10:27:08Z

Tijuca: working on the formating

This is a pretty rough guide at this point, but I felt compelled to put something down after spending many hours searching for a solution to obtain emails from ZM events. In the end the solution is relatively simple:

Prerequisites: Basically command line knowledge, ability to use text editors.

1. Install, configure, and test Postfix.

Postfix is a full featured mail server. That said, the scope of this guide is merely to configure it for use as an "smtp" relay for Gmail. In other words, we'll be using our gmail account credentials and their system to relay our event alert mail. I found the following guide on the internet and used it to configure and test Postfix successfully:

A. Install

(Note the following install commands are based on yum/Fedora. Alter based on your distribution

Install Postfix and cyrus-sasl with your application manager of choice. If you're compiling from source, be sure to make Postfix with the -DUSE_SASL_AUTH flag for SASL support and -DUSE_TLS for TLS support.

$ '''yum install postfix cyrus-sasl'''

Stop the sendmail service

$ '''/etc/init.d/sendmail stop'''

Remove sendmail from the startup runlevels

$ '''chkconfig --del sendmail'''

B. Configure Postfix as Gmail SMTP relay

If you're attempting to relay mail using Gmail, then it will be necessary to use TLS with Postfix. You'll have to point Postfix at your server's trusted CA root certificate bundle, but luckily "...client-side certificates are not required when relaying mail to GMail".

1. First, double-check that Postfix was configured with SSL support (ie. ldd should return at least one line starting with libssl):

$ '''whereis -b postfix'''
postfix: /usr/sbin/postfix /etc/postfix /usr/libexec/postfix

$ '''ldd /usr/sbin/postfix'''
libssl.so.6 => /lib/libssl.so.6 (0x00111000)

2. Now we need to find your server's CA root certificate bundle, which is typically distributed with openssl. The bundle file is used by Postfix to verify Gmail's SSL certificate (signed by Thawte). On my CentOS server, this file was located at /etc/pki/tls/certs/ca-bundle.crt, but may be in a different location on your box (ie. /etc/ssl/certs). Mine was in /usr/share/doc/mutt.

$ '''locate ca-bundle.crt'''
/etc/pki/tls/certs/ca-bundle.crt

3. Edit /etc/postfix/main.cf with the following values (edit-Postfix comes with a predefined template, I moved that to main.cf.bak and used Nano to create a blank file for the following content. It was cleaner when it came to testing as the template comes with a bunch of text explanation for each setting. If you're blindly following a guide like this one, it just all gets in the way):

Copy/paste the following into a blank "/etc/postfix/main.cf" file using your favorite text editor (I like Nano):

'''relayhost = smtp.gmail.com:587'''
'''mydomain = local.domain'''
'''myhostname = host.local.domain'''
'''myorigin = $myhostname'''
'''smtpd_sasl_path = smtpd'''
'''smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd'''
'''smtp_sasl_type = cyrus'''
'''smtp_sasl_auth_enable = yes'''
'''smtp_sasl_security_options = noanonymous'''
'''smtp_sasl_tls_security_options = noanonymous'''
'''smtp_use_tls = yes'''
'''smtp_tls_CAfile = /path/to/your/ca-bundle.crt'''
'''smtp_sasl_tls_security_options = noanonymous'''

4. Copy/paste the following into a blank "/etc/postfix/sasl_passwd" file. Change username & password to your gmail username and password of course.

'''# The server info must exactly match the value'''
'''# for "relayhost" in /etc/postfix/main.cf'''
'''smtp.gmail.com:587 username:password'''

5. Generate a postfix lookup table from the previous file

$ '''postmap hash:/etc/postfix/sasl_passwd'''

5a. Make sure that the hash "took" by checking it with the following command, the response should be the user:pass that you defined for the file. Basically, we're confirming that Postfix has the ability to pull up the user:pass when it needs it and you didn't hose the command with the wrong path or file name or something:

'''postmap -q': postmap -q smtpout.secureserver.net /etc/postfix/sasl_passwd'''

6. Get rid of the clear text password file (I'd really do this at the end, once it's confirmed functional, but don't forget)

$ '''rm /etc/postfix/sasl_passwd'''

C1. Restart postfix and send a test email

$ '''postfix reload'''
$ '''sendmail email@example.com'''
'''Test relay thru Gmail'''
'''.'''

2. Go check your the email account you sent your test email to.

3. Troubleshooting

Monitor postfix mail log in a separate session with the following command

$ '''tail -f /var/log/maillog'''

If the log is displaying the following error
...
(Authentication failed: cannot SASL authenticate to server ...: no mechanism available)
...

Then set this variable in /etc/postfix/main.cf

'''smtp_sasl_security_options = noanonymous'''

If the log is displaying this error:
"553 Sorry, that domain isn't in my list of allowed rcpthosts. (in reply to RCPT TO command)"
Check your username and password in /etc/postfix/sasl_passwd. Your user name is usually your full email address. If you have to fix it, don't forget to use postmap to generate a new lookup table.

2. Configure ZoneMinder. There's not really alot to this. Many of the forum posts I checked had me altering zmfilter.pl with User & Pass Auth values and suggesting ssmtp instead of smtp and so on... I didn't have success with those methods. With Postfix installed and confirmed running, zmfilter.pl doesn't need to be modified in any way, so if you've already altered it, back those changes out or restore the backup you should have made.

I won't get into alot of detail on each field of the "email" tab in "options", but thats where you need to be.. you need to put in your to email and your from email address and your smtp server. That's the only thing specific to this guide, the smptp, server, don't put gmails there, since we've configured Postfix with all that. Just put in "localhost". That's really it. That's all there is that's specific on the ZM side to getting ZM working with Postfix. Pretty simple huh.. You can play around with email content settings later. That's out of scope for this guide, we're just trying to get something/anything on the other end of the pipe...

C. Generate an alert event if you don't have one already and create a filter that sends an email. Refer to the docs for that step.. it's basic stuff.. all you have to do is create a filter that will pick up at least one event and then tick the email box and click execute. If you click save and then tick the "run filter in background" option it'll sit there and wait for an event to occur (according to your filter properties) and automatically shoot an email out to you. Cool.

Note:
This is a rough guide (no pretty formatting or anything), but it got the job done quickly and easily for me after I'd spent maybe 48 hours combined pursuing other blind allies.. Good luck. Huge thanks to a guy named Tim White at Zulius for putting together the Postfix portion of this guide.

Good Luck!

Debian Squeeze

2011-07-31T11:18:27Z

Tijuca: /* Preparations */ fixing formating

==Zoneminder on Debian Squeeze==
Installation of Zoneminder on an Squeeze System

The installation on an Debian system is very easy, because the complete zoneminder software is packaged for all Debian platforms. The current version in Squeeze for Zoneminder is 1.24.2.

===Preparations===
If you will not use USB or IP cameras please be sure the capture card is working well. First be sure the card supported by the kernel. You can test this with a simple <code>lspci -v</code> with root privileges. Every channel will be shown as a seperate entry. Look for something similar '''...SAA71xx...'''.<br/>
Take also a look at the used kernel modul.

...
04:08.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:09.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0a.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01))
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcfd000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0b.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcfc000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0c.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcfb000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0d.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfa000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0e.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcf9000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0f.0 Multimedia controller: '''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcf8000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''
...

As you can see there are 8 channels. We will find them (hopefully :-) )in the devfs filesystem.
ls -ls /dev/video*
0 crw-rw----+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw----+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw----+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw----+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw----+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw----+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw----+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw----+ 1 root video 81, 14 30. Jul 15:17 /dev/video7
That looks not bad, but there will be problems later. We see every entry is owend by the user 'root' und the group 'video'. But zoneminder will run with www-data rights, so with this constellation zoneminder can't access the devfs entrys. So the easiest way ist to used a special udev rule that changed the ownership of the dev entrys. Let's create this rule. Create a file <code>/etc/udev/rules.d/90-zoneminder.rules</code>.
vi /etc/udev/rules.d/90-zoneminder.rules
and put the following stuff into, this will set the mode of the /dev/video* files to 0666
# allow non-privileged users to access the /dev/video* files
SUBSYSTEM!="video4linux", GOTO="zm_rules_end"
SUBSYSTEM=="video4linux", MODE="0666", GROUP="video"
LABEL="zm_rules_end"
After reloading the udev rules the entrys will look like this:
ls -ls /dev/video*
0 crw-rw-rw-+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw-rw-+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw-rw-+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw-rw-+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw-rw-+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw-rw-+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw-rw-+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw-rw-+ 1 root video 81, 14 30. Jul 15:17 /dev/video7

===Installation===
The installation is really simple, just type <code>apt-get install zoneminder</code> with root privileges.

That's all. Now you have to setup your zoneminder under <nowiki>http://localhost/zm</nowiki> .

Debian Squeeze

2011-07-31T11:17:15Z

Tijuca: try to discribe installation of zoneminder in debian squeeze

==Zoneminder on Debian Squeeze==
Installation of Zoneminder on an Squeeze System

The installation on an Debian system is very easy, because the complete zoneminder software is packaged for all Debian platforms. The current version in Squeeze for Zoneminder is 1.24.2.

===Preparations===
If you will not use USB or IP cameras please be sure the capture card is working well. First be sure the card supported by the kernel. You can test this with a simple <code>lspci -v</code> with root privileges. Every channel will be shown as a seperate entry. Look for something similar '''...SAA71xx...'''.<br/>
Take also a look at the used kernel modul.

...
04:08.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:09.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0a.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01))
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcfd000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0b.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcfc000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0c.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcfb000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0d.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at fdcfa000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0e.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fdcf9000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''

04:0f.0 Multimedia controller: ''''Philips Semiconductors SAA7130 Video Broadcast Decoder''' (rev 01)
Subsystem: Philips Semiconductors Behold TV 401
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdcf8000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
'''Kernel driver''' in use: '''saa7134'''
...

As you can see there are 8 channels. We will find them (hopefully :-) )in the devfs filesystem.
ls -ls /dev/video*
0 crw-rw----+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw----+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw----+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw----+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw----+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw----+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw----+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw----+ 1 root video 81, 14 30. Jul 15:17 /dev/video7
That looks not bad, but there will be problems later. We see every entry is owend by the user 'root' und the group 'video'. But zoneminder will run with www-data rights, so with this constellation zoneminder can't access the devfs entrys. So the easiest way ist to used a special udev rule that changed the ownership of the dev entrys. Let's create this rule. Create a file <code>/etc/udev/rules.d/90-zoneminder.rules</code>.
vi /etc/udev/rules.d/90-zoneminder.rules
and put the following stuff into, this will set the mode of the /dev/video* files to 0666
# allow non-privileged users to access the /dev/video* files
SUBSYSTEM!="video4linux", GOTO="zm_rules_end"
SUBSYSTEM=="video4linux", MODE="0666", GROUP="video"
LABEL="zm_rules_end"
After reloading the udev rules the entrys will look like this:
ls -ls /dev/video*
0 crw-rw-rw-+ 1 root video 81, 0 30. Jul 15:18 /dev/video0
0 crw-rw-rw-+ 1 root video 81, 2 30. Jul 15:18 /dev/video1
0 crw-rw-rw-+ 1 root video 81, 4 30. Jul 15:43 /dev/video2
0 crw-rw-rw-+ 1 root video 81, 6 30. Jul 15:43 /dev/video3
0 crw-rw-rw-+ 1 root video 81, 8 30. Jul 15:17 /dev/video4
0 crw-rw-rw-+ 1 root video 81, 10 30. Jul 15:17 /dev/video5
0 crw-rw-rw-+ 1 root video 81, 12 30. Jul 15:17 /dev/video6
0 crw-rw-rw-+ 1 root video 81, 14 30. Jul 15:17 /dev/video7

===Installation===
The installation is really simple, just type <code>apt-get install zoneminder</code> with root privileges.

That's all. Now you have to setup your zoneminder under <nowiki>http://localhost/zm</nowiki> .

Debian

2011-07-31T10:04:14Z

Tijuca: /* Installation Guides */ adding "Debian Squeeze"

[http://www.debian.org/ Debian GNU/Linux] is a free operating system with a focus on stability. It's based on a sophisticated package management system that lets you choose from three releases of varying stability. The software packages included in the ''stable'' release have been tested thoroughly and are ideal for a server environment, whereas ''testing'' and ''unstable'' releases have more recent versions of software which usually contain some bugs. Ironically, Debian's ''unstable'' release is often more stable than many other distributions' final releases.

==Installation Guides==

Zoneminder is now in Debian "unstable" (as of 2007-03-12) so you should be able to just "apt-get install zoneminder" if you include
"unstable" packages. Alternately:

*[[Debian 3.1 install|Debian 3.1 + Zoneminder 1.22.x]] Installation Guide (ZM from source - without ffmpeg) using ''stable'' packages

*[http://www.zoneminder.com/fileadmin/downloads/ZoneMinder_install.doc Debian + ZM] Installation Guide (using a [http://www.spic.net/zoneminder/ debian ZM package] requiring ''unstable'' ffmpeg/libavcodec2/liblame0)

*[[Debian Etch]] The above are outdated
*[[Debian Squeeze]]

*[http://www.csquad.org/cocoon/tags/public/zoneminder/zoneminder.html Debian Etch + ZoneMinder 1.23.x in French] Installation Guide for Debian in French.

You can also use the following guide to install Zoneminder from source in a Debian Lenny based machine. The guide is in spanish and the repositories used are from Chile. If you want to, just use the ones of your country in your sources.list file:

*[http://www.zenner.cl/Instalacion%20de%20ZONEMINDER%20en%20Debian%20Lenny.pdf Debian Lenny + Zoneminder 1.24 in spanish]

*[http://www.freehoster.cn/howto.txt Debian 5 Lenny + Zoneminder 1.24 mit Spectra8 Karte in deutsch]

*[http://www.rmacd.com/howto/zoneminder-debian-lenny-install.php Debian Lenny and ZM1.24 (all '''stable''') May 2010 (English)]

==Installation Notes==
[[Debian init.d|/etc/init.d/zm script]] - slightly modified from the original to correctly echo output on debian

http://www.zoneminder.com/forums/viewtopic.php?t=5391

http://www.zoneminder.com/forums/viewtopic.php?t=6215

http://www.zoneminder.com/forums/viewtopic.php?t=5892

:./configure --with-mysql=/usr
:--with-webdir=/var/www/zm
:--with-cgidir=/var/www/cgi-bin --sysconfdir=/etc
:--with-ffmpeg=/usr/local
:--with-webuser=www-data
:--with-webgroup=www-data CPPFLAGS="-I /usr/local/ssl/include -I /usr/local/lib"

== Additional Notes ==
http://www.zoneminder.com/forums/viewtopic.php?t=6261
<nowiki>Insert non-formatted text here</nowiki>