On Tue, 2009-03-17 at 06:44 +0100, Aurelien Jarno wrote: > On Mon, Mar 16, 2009 at 09:00:25PM -0700, Ross Boylan wrote: > > Package: lm-sensors > > Version: 1:3.0.2-1+b2 > > Severity: normal > > > > > > Subject: lm-sensors: ignore in sensors.conf has no effect on output of > > sensors or sensord > > Package: lm-sensors > > Version: 1:3.0.2-1+b2 > > Severity: normal > > > > I added a bunch of ignore lines to my sensors.conf, but the ignored sensors > > are still > > reported by sensors run on the command line and by sensord. > > > > The docs do note that the ignore specification is only advisory, so I > > suppose it's possible > > this is not a bug. In that case, please consider this wishlist. However, > > it seems > > unlikely the basic apps are ignoring this. It seems more likely I've > > misunderstood > > something or there is a real bug. > > > If you are using lm-sensors version 3, you should do the change to > /etc/sensors3.conf. /etc/sensors.conf is for applications still using > the old version of the library. > Thank you. That works much better :)
Looking at the docs now, I see this info in there in several places. sensord's README.Debian mentions sensors.conf only. Many of the man pages mention sensor.conf and sensor3.conf. They could be a bit clearer that this is version 3. Would it be possible not to create sensor.conf for new installs? I have a brand new Lenny system and added lm-sensors and sensord (and dependencies and suggestions). If this was all v3, why did it create sensors.conf? Actually, I'm assuming they created it; maybe it was already there. So, my problem is solved. It might help others to tweak things to make the use of sensor3 a bit clearer. Thanks. Ross -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
