matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

[sensors]: Workaround for apparent bug in lm-sensors (#1058)

Browse Source
This commit is contained in:
Joe LeVeque 2017-10-20 11:01:26 -07:00 committed by GitHub
parent 8bc6b55331
commit def0f2e4de
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
dockers/docker-platform-monitor/lm-sensors.sh
View File

@ -3,7 +3,19 @@
# Based off /etc/init.d/lm-sensors
#
/usr/bin/sensors -s > /dev/null 2>&1
# NOTE: lm-sensors v3.3.5 appears to have a bug. If `sensors -s` is called, it
# will first load /etc/sensors.conf, then load all files in /etc/sensors.d/,
# overriding any values that may have already been specified in
# /etc/sensors.conf. However, it appears this overriding is not taking place.
# As a workaround, as long as a platform-specific sensors.conf has been copied
# to /etc/sensors.d/, we will ONLY load that file, otherwise we load the default.
if [ -e /etc/sensors.d/sensors.conf ]; then
/usr/bin/sensors -s -c /etc/sensors.d/sensors.conf > /dev/null 2>&1
else
/usr/bin/sensors -s > /dev/null 2>&1
fi
/usr/bin/sensors > /dev/null 2>&1
# Currently, there is no way to run sensord in the foreground, so we