Hardware Sensors Indicator

indicator-sensors-daily DEBUG floods log?

Asked by Vindicator

I was looking at journalctl for something in particular when I saw an immense flood of DEBUG statements that I assume is coming from the daily version of indicator-sensors:
*****
Nov 13 03:46:41 <machineName> gnome-session[1812]: [dynamic] DEBUG: Got existing rate data for sensor: Core 1 - rate: 0.471212, last_value 28.000000, last_time 114051847
Nov 13 03:46:41 <machineName> gnome-session[1812]: [dynamic] DEBUG: abs rate of change of sensor Core 1: 0.599902 (t0: 31.000000, t-1: 28.000000, dv: 3.000000, dt: 5.000814)
Nov 13 03:46:41 <machineName> gnome-session[1812]: [dynamic] DEBUG: EWMA abs rate of change of sensor Core 1: 0.496950
*****
Is this expected from the daily project?
Is there a configuration setting that can be changed by the user?

Question information

Language:
English Edit question
Status:
Expired
For:
Hardware Sensors Indicator Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Grzegorz Brzezinka (6-inf2-g) said : 		#2

I have seen exactly the same behaviour. The syslog is flooded by:
DEBUG: Got existing rate data for sensor: CPU - rate: 0,674674, last_value 47,000000, last_time 17901823097
Mar 10 13:39:33 greg-laptop gnome-session[4056]: [dynamic] DEBUG: abs rate of change of sensor CPU: 0,066670 (t0: 46,000000, t-1: 47,000000, dv: -1,000000, dt: 14,999204)
Mar 10 13:39:33 greg-laptop gnome-session[4056]: [dynamic] DEBUG: EWMA abs rate of change of sensor CPU: 0,553073

Revision history for this message
father_ted (paulfourie-x) said : 		#3

Not immediately. It takes a few days and then really goes Berserk.