ZoneMinder Forums

Reinstalled Feisty to get a clean install platform.

installed the deb package from this site. dpkg installed all of the prereqs automatically.

3 steps to joy -

had to link the apache.conf file to zoneminder.conf per the readme.deb
had to chmod 666 the /dev/video0 device ( if I add www_data to the video group this will probbably go away)
had to dpkg-reconfigure dash to bash behavior

reloaded apache2, then off to the races....

running just fine. I still get the runaway process (described in the memory leak thread) but I am now convinced that is due to a driver error. If I run from a remote machine, all of the windows work with no errors.

Another bug - when I enable authentication, cameras will not stream to the browser. Disable it and they start working again. Console access works fine, just no streams...

Did you restart all the ZM services after making the change?
All the ZM services must be restarted so that they have all the new settings past to them.

John Williams wrote:Reinstalled Feisty to get a clean install platform.

i had to dpkg-reconfigure dash to bash behavior

Still trying to track that one down; but that's my main focus (as it's holding open a bug in the Debian BTS too)

Thanks Cordel, will give that a try. Did not restart ZM...

BTW, with this morning's updates, all my Ubuntu 7.04 problems are gone. I am running RAID1 on all of my partitions and was having a reboot problem.

My crappy capture card - I am going to upgrade it soon, as soon as I determine what to buy.

Any recommendations on a 120fps BTTV card with 4 chips instead of the multiplexed single one? Lots of cards out of stock at bluecherry.

Going to buy the Sony based bullet camera. That looks to be a good price/performer.

Cordel,

nph_zms to zms change fixed leak problem. thx...

Auth still not working. Tried it using a restart of both ZM and apache2. While watching TOP I see no zms process starting. Will scan the logs later today. Got to go mow the yard now...

Check the logs for your Auth problem...
zmdc, zmwatch, messages, and apache error_log.

Something in there should give some detail of what is amiss.