ZoneMinder Forums

I would recommend using the MxPEG stream and the linux converter to mjpeg

iconnor! good to hear. I actually have already re-patched all my work into trunk with mastertheknifes performance patch and was planning to release an updated version. I then heard MTK's patch was going to be into the next release so I figured I would wait until then to release my version so that yo...

Its probably a security catch:) It should be:
Error( "%s", e.getMessage().c_str() );

You cannot recover all the meta data obviously if you lost the entire database but if you are decent at coding in any language you should be able to insert enough entries and fake data to be able to view events and using file timestamps to have them properly dated.

For some reason I did not get the notifications from the forum or somehow missed the replies. I did a quick check today over it and its still playing with fire (but such is most of the ZM code and I am not sure that will change any time soon). Going the escape route i think you are getting pretty cl...

no it did not, neither the improvements or bug fixes sadly! Maybe next version:)

Sorry if you still have the camera let me know, there are some things we can try but it should be fairly easy to get it working properly.

I wanted to first thanks the eyeZm guys for contributing back the code to trunk. It moves another step towards a better XML interface for ZM and that only means more apps and making ZM even better. With that said it may be a good idea to disable the code by default or perform a code review of it. Th...

I think it may be a better idea to try one shared database among several servers, all you are looking to do is really avoid it starting the zmc daemon (and zma technically to save the log files). I would add a field in the database for what server the camera is supposed to run on, then in the daemon...

Its been honestly awhile since i worked in the ZM code, a good reason is probably the ERR call prints the error and bails out (abort) where as an INFO wouldn't. In the case of the stream being broken you want to abort so rather than have a separate abort but INFO handler just called the same.

Yes, the message is good that means it detected the stream was broken and stops, if it didn't it could continue to run forever.

Sorry, to solve the problem someone needs to write a parser to just split the jpeg image in half and send out two seperate ones for zm. It wouldn't be that complex but will take a programmer to do it.

cambozola shouldnt be required for FF.

wc -w prints the number of words and is absolutely useless. But ls -lah /proc/PID/fd will work just fine also.

install the tool lsof then run it with the -p option with the pid of the zmwatch leaking( IE: lsof -p 19213) pastebin the results. My zmwatch doesn't leak like this but this should atleast list what file handles are leaking.