In have an area, that I'm guarding with zm, but due to sun light changes it gives me a lot of false alarms.
So, I'm changing MinPixelThreshold field in Zones table during the time of the day.
I noticed that killing -HUP zma pids doesn't reload the new MinPixelThreshold settings from the db. Neither does with -TERM.
Restarting zm with zmpkg.pl does the trick, but this gives a small downtime (~ 10 seconds).
Looking in the src I can see, for example, that HUP signal triggers eventually ReloadZones() -> Zone::Load() which reloads all zone settings, but in my case I don't think that it does. Am I I correct or I'm missing something?
Btw, I have version 1.24.2 (ubuntu 11.04 package).
I've also tried a different approach, by using the zmdc.
First, I enabled the debug mode and then I restarted zma with zmdc. For example: zmdc.pl restart zma -m 4
Then, I checked the debug log for MnAT (I suppose this is the MinPixelThreshold value):
/tmp/zm_debug.log.16145:04/22/12 14:01:19.799402 zma_m4.DB1-zm_zone.cpp/50 [Initialised zone 30/top_area - 1 - 215x231 - Rgb:ff0000, CM:3, MnAT:25, MxAT:0, MnAP:3746, MxAP:0, FB:3x3, MnFP:2809, MxFP:0, MnBS:2341, MxBS:0, MnB:1, MxB:0, OF: 0]
, but it doesn't change.
It changes only if I restart zma with zmdc 2-3 times.
My guess is that I'm missing something. So, the question is, what's the safest way to change MinPixelThreshold value from db directly and the have it applied in zma processes?
Forum for questions and support relating to the 1.24.x releases only.
1 post • Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 1 guest