On Wednesdayen den 4 July 2007 04.17.30 you wrote:
> On 03/07/07, Per-Olov Sjvholm <[EMAIL PROTECTED]> wrote:
> > Hi Misc
> >
> >
> > I am probably missing something, but what..
> >
> >
> > sensorsd says in the syslog that the sensor is "within limits" even
> > though a "sysctl -a|grep sensor" shows that it is not.
> >
> >
> > Are there any known bugs? I have checked the list and cannot find
> > anything related to this... I run a Dell PE830 on OpenBSD 4.0 stable
> > (latest update in May 25:th). I have these sensors which appears to
> > always show the correct values running a "sysctl -a|grep sensor".
> > hw.sensors.0=ipmi0, Temp, 43.00 degC, OK
> > hw.sensors.1=ipmi0, Planar Temp, 38.00 degC, OK
> > hw.sensors.2=ipmi0, CMOS Battery, 3.13 V DC, OK
> > hw.sensors.3=ipmi0, Back Fan, 2204 RPM, OK
> > hw.sensors.4=ipmi0, Intrusion, Off, OK
> > hw.sensors.5=ami0, sd0, drive online, OK
> >
> >
> >
> > From sensords.conf
> > hw.sensors.0:high=42C:command=/bin/echo "test test"|/usr/bin/mailx -s
> > "Sensor warning: CPU temp over %2 bla bla bla" MYEMAIL
> > hw.sensors.1:high=39C:command=/bin/echo "test test"|/usr/bin/mailx -s
> > "Sensor warning: Chassie temp over %2 bla bla bla" MYEMAIL
> >
> >
> > Starting sensorsd and look at /var/log/daemon
> > Jul 3 16:12:22 xanadu sensorsd[14634]: hw.sensors.0: within limits,
> > value: 43.00 degC
> > Jul 3 16:12:22 xanadu sensorsd[14634]: hw.sensors.1: within limits,
> > value: 38.00 degC
> >
> >
> > I assume I receive no reports as the daemon say the sensor wrongly is
> > within the limits....
>
> Please, check the manual page for your system [0], specifically, the
> following:
>
> Sensors that provide status (such as from bio(4), esm(4), or ipmi(4))
> do not require boundary values specified (that otherwise will be ignored)
> and simply trigger on status transitions.
>
> In other words, for those sensors that provide the status themselves,
> the keywords "high" and "low" in sensorsd.conf have no effect. This
> limitation was removed at c2k7 [1], and the newest sensorsd in OpenBSD
> 4.1-current allows you to set your own limits for any sensor, and
> ignore the status that the sensor device itself provides.
>
> So if you need this functionality, you may wish to upgrade to OpenBSD
> 4.1-current.
>
> Alternatively, you may upgrade to OpenBSD 4.1-stable that has the new
> two-level sensor framework, and then manually update sensorsd to
> 4.1-current (files /usr/src/{etc/sensorsd.conf,usr.sbin/sensorsd/*}),
> compiling and installing it afterwards -- sensorsd in 4.1-current as
> of today is source-code-compatible with 4.1-stable (note that it is
> not binary compatible). However, please be warned that mixing
> 4.1-stable and 4.1-current is not officially supported, so use it at
> your own risk! (Even though it works for me in this specific case with
> sensorsd.)
>
> Cheers,
> Constantine. :)
>
> [0]
> http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf&sektion=5&manpat
>h=OpenBSD+4.0
>
> [1]
> http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/sensorsd/sensorsd.c#rev1
>.32
Thanks for the answer
So I only need the "command" with %1-%4 and no "low"/"high" specs in
sensorsd.conf? The trigger will come when Dell think the temp i to low or
high? If so... Is there a way of knowing at what temperature this happends. I
mean, could you ask the hardware itself with any software, or do I have to
dig into some of Dell:s docs? That is not super important, but it would be
nice to know at what value it happends, and if possible test it.
Also, isn't it possible then to have different commands for low and high if
low and high has no meanings? I mean, do I have to take care of if it's a low
or a high warning in the command script. If low and high have meanings (as in
OBSD 4.1-current) I could have one sensor row in sensorsd.conf for high and
one for low with different commands. Right?
You said that:
"Alternatively, you may upgrade to OpenBSD 4.1-stable that has the new
two-level sensor framework" Why do I need to go to -CURRENT if it's included
in 4.1-STABLE? Isn't 4.1-STABLE ok? I want to avoid -current on production
servers. But after looking at
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/sensorsd/sensorsd.c it
seems I am *not* OK with just 4.1 STABLE, and that I need -CURRENT if I want
this functionality...
Per-Olov
--
GPG keyID: 4DB283CE
GPG fingerprint: 45E8 3D0E DE05 B714 D549 45BC CFB4 BBE9 4DB2 83CE
GPG key:
http://keyserv.nic-se.se:11371/pks/lookup?op=get&search=0xCFB4BBE94DB283CE
