With sensord use flag enabled, lm_sensors-3.1.1 will install /etc/conf.d/sensord and also the init script for sensord, but does not install /usr/sbin/sensord. Also the init script should be updated to reflect the new configuration file of /etc/sensors3.conf. Reproducible: Always Steps to Reproduce: 1. emerge lm_sensors-3.1.1 with sensord use flag 2. try to start sensord 3. Actual Results: sensord init script fails because /etc/sensors.conf does not exist. Updating the init script manually to use /etc/sensors3.conf results in sensord fails to start because it is no longer on the system. Expected Results: /usr/sbin/sensord is on the system and the init script points to the correct conf file. Masking lm_sensors-3.1.1 and using lm_sensors-3.0.3 results in a working /usr/sbin/sensord, but the init script still needs to be pointed at the correct file for it to actually work.
Same problem here. And i can confirm the posted solution works fine.
Kernel 2.6.31 went stable, and apparently needs lm_sensors 3.1.1, so this may be a little higher priority now...
The 1.2 version of the ebuild linked bug 244598 seems to install sensord.
(In reply to comment #3) > The 1.2 version of the ebuild linked bug 244598 seems to install sensord. Sorry. No it doesn't.
this is fixed in cvs. please test and report back, if it does not work... thanks for the reports. have fun ;-)
Confirmed this is fixed. emerge --sync; unmask lm_sensors-3.1.1 on my system; emerged lm_sensors-3.1.1 and all is well. Thanks.