Basil Chupin wrote:
Only problem with this is that lm_sensors application was not actually activated :-) . All I had in place was the lm_sensors file created by /usr/sbin/sensors-detect. I realize I rebuilt the sensors package I am using, but it is not that different than the SuSE 10.1 default. The file /etc/sysconfig/lmsensors is just variables. I just checked the rpm, and I guess things have changed because there is a file listed /etc/init.d/lm_sensors. So out of the box it has the capability to get started, but according to the spec file, it doesn't start by installing the package.
Unless of course in SUSE 10.1 the lm_sensors are activated automatically once the lm_sensors file is created in /etc/sysconfig. Dunno. I don't think so, but IIRC sensors-detect loads some of the modules (all?) which would cause it to start working til it was stopped (which unloads the modules).
Actually..... I just had a look at the lm_sensors file and I think lm_sensors may be activated should the lm_sensors file exist in /etc/sysconfig which may go against what Joe Morris mentioned in an earlier message. But then I am stating this from a very cursory look at what is shown in lm_sensors file.
It is sourced from the startup script, so it would only work if the service had been started (i.e. via Runlevel Editor, etc.). Outside of that, it is only variables. It actively does nothing. BUT, sensors-detect may load the modules needed to work, I'm not sure, but it does not use or need /etc/sysconfig/lm_sensors.
BTW, here are the parameters which sensors-detect put into the lm_sensors file when it created it:
# Generated by sensors-detect on Sat Sep 9 01:07:41 2006 MODULE_0=i2c-nforce2 MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=it87 Similar to mine. MODULE_0=i2c-nforce2 MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=w83627hf
BTW, you should change the module modprobed in lines 38 and 45 in /etc/init.d/lm_sensors to i2c-dev, which was the reason I rebuilt the package I am using. -- Joe Morris Registered Linux user 231871