With one of my last rat eaten, open gate, (drive-through-cpu) Intel firewalls replaced, I have a trivial issue with the sensors daemon in Ipfire on the new firewall hardware.
It is well known that the sensors “ALARMS” are mopstly and usually always incorrect or false positive, except for CPU temps that usually work reasonably reliably.
However, the problem is that sensors trigers the built in ALARM on the mobo, once all the sensors are in status “ALARM”. To note ALL theses alarms are false positive. There uis no overheating and no voltages dropped top zero. The firewall works perfectly.
I need to uninstall sensors on IPFIRE as I cannot manage to find the usual daemon in init.d to stop the sensord daemon.
Since IPFIRE does not have apt (understandable !) and very little default sysadmin tools (not even whereis among others) -again understandably, I need to know what the easiest way is to find and remove the sensors daemon so that the alarm is not triggered as all the errors are utterly bogus.
Here is an example of the current state. In a day it will all be set to “ALARM” and the Alarm on the mobo will sound. --annoying.
coretemp-isa-0000 Adapter: ISA adapter Core 0: +38.0C (crit = +100.0C) Core 1: +40.0C (crit = +100.0C) w83627dhg-isa-0000 Adapter: ISA adapter Vcore: 1.16 V (min = +0.72 V, max = +1.39 V) in1: 1.05 V (min = +0.94 V, max = +1.16 V) AVCC: 3.31 V (min = +2.96 V, max = +0.00 V) ALARM +3.3V: 3.31 V (min = +1.62 V, max = +3.58 V) in4: 1.53 V (min = +1.35 V, max = +0.00 V) ALARM in5: 1.28 V (min = +1.13 V, max = +1.38 V) in6: 1.87 V (min = +1.62 V, max = +2.00 V) 3VSB: 3.31 V (min = +2.96 V, max = +3.63 V) Vbat: 3.07 V (min = +2.96 V, max = +1.25 V) ALARM fan1: 0 RPM (min = 10546 RPM, div = 128) ALARM fan2: 0 RPM (min = 10546 RPM, div = 128) ALARM fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM fan4: 0 RPM (min = 0 RPM, div = 128) ALARM fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM temp1: +46.0C (high = +75.0C, hyst = +70.0C) sensor = thermistor
As an example here