Your message dated Mon, 02 Jul 2018 10:30:26 +1000
with message-id <73073936.taLP5m7YSW@deblab>
and subject line Done: ZM_TELEMETRY_DATA=no in /etc/zm/zm.conf not effective
has caused the Debian Bug report #858672,
regarding ZM_TELEMETRY_DATA=no in /etc/zm/zm.conf not effective
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
858672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858672
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zoneminder
Version: 1.30.0+dfsg-2

Per /usr/share/perl5/ZoneMinder/ConfigData.pm, ZoneMinder has a
configuration variable ZM_TELEMETRY_DATA that can be set to "yes" (the
default) or "no" to respectively enable or disable automatic
transmission of usage information to the ZoneMinder upstream.

I don't care for opt-out "telemetry" of this sort, so I added
ZM_TELEMETRY_DATA=no to the /etc/zm/zm.conf file prior to starting
ZoneMinder for the first time. Unfortunately, when I started ZM, the log
file showed these entries:

    2017-03-24 23:26:56.638730 zmtelemetry[1722].INF-zmtelemetry.pl [Sending 
data to ZoneMinder Telemetry server.]
    2017-03-24 23:26:56.880710 zmtelemetry[1722].INF-zmtelemetry.pl [Telemetry 
data uploaded successfully.]

Frustrating, to say the least.

I have already added ZM_CSS_DEFAULT=flat to this file successfully, so
the syntax and variable name should be correct.

--- End Message ---
--- Begin Message ---
TELEMETRY_DATA is a database option that can be changed only in

 Options --> System --> TELEMETRY_DATA

using web interface.

I agree that some options do not belong to database but that's a historical 
design decision/flaw. See the following upstream bug for insights into 
similar problem:

 https://github.com/ZoneMinder/zoneminder/issues/790

IMHO Paths should definitely be in "/etc/zm/zm.conf" (and upstream is already 
improving that) but other options like "ZM_TELEMETRY_DATA" don't have to be 
in the config file. Upstream may have different opinion about that.
Anyway there is little we can do about it here so I would recommend to 
discuss the matter with upstream, in their bug tracker:

 https://github.com/ZoneMinder/zoneminder/issues

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to