default sensorsd.conf change
Constantine Aleksandrovich Murenin
C++ at Cns.SU
Wed May 25 14:35:56 PDT 2016
Lack of the decimal places in sensorsd.conf has never been an issue
with sensorsd on OpenBSD; is DragonFly's strtod(3) somehow different
to the one in OpenBSD?
I think the issue you're encountering is instead documented in the
CAVEATS part of sensorsd.conf(5):
173Alert functionality is triggered every time there is a change in
174for example, when
175.Xr sensorsd 8
177the status of each monitored sensor changes
178from undefined to whatever it is.
On 25 May 2016 at 14:04, Lanir <lanir at cisns.net> wrote:
> Can someone change the default /etc/sensorsd.conf file (if it hasn't
> been updated in a change I missed already)? The value it's checking has
> 2 places after the decimal which confuses sensorsd, since the default
> sensorsd.conf file is set to "high=85C" with no decimal places.
> Here's the header of the file I had in case it's changed:
> # $OpenBSD: sensorsd.conf,v 1.8 2007/08/14 19:02:02 cnst Exp $
> # $DragonFly: src/etc/sensorsd.conf,v 1.1 2007/10/02 12:57:00 hasso Exp $
> And here's the new default config line I'd recommend:
> Current default behavior is somewhat surprising; system always shuts
> down no matter the temperature a minute or two after sensorsd starts
> running. Amusing on a local system, probably not so much on a remote one.
More information about the Users