We disabled health and crash reporting in the prefs.js, but timestamp does not update and they are enabled- how often do they re-enable themselves?
In a public account, one where the prefs.js is not updated often, we set user_pref("datareporting.healthreport.service.enabled", false) , but found that even with that set, after some time, apparently related to the timestamp, both heath and crash reporting appears to be enabled again. What is the time duration that goes by before we must update the prefs.js to keep the crash ahd health reporting disabled?
All Replies (1)
I use these lines in mozilla.cfg.
lockPref("datareporting.sessions.current.main", 0);
lockPref("datareporting.sessions.currentIndex", 0);
defaultPref("datareporting.healthreport.uploadEnabled", false);
defaultPref("datareporting.policy.dataSubmissionEnabled", false);
defaultPref("datareporting.healthreport.service.enabled", false);
defaultPref("toolkit.telemetry.rejected", true);
defaultPref("toolkit.telemetry.unified", false);
defaultPref("toolkit.telemetry.unifiedIsOptIn", false);
defaultPref("toolkit.telemetry.server", "");
You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences. A local-settings.js file needs to be placed in the "defaults/pref" folder where also the channel-prefs.js file is located to specify using mozilla.cfg.
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
These functions can be used in the mozilla.cfg file:
defaultPref(); // set new default value pref(); // set pref, allow changes in current session lockPref(); // lock pref, disallow changes
The mozilla.cfg file needs to start with a comment line (//).
See Configuration:
See also: