Levi Bard wrote:
> If you google for your motherboard's model (or post it to the list),
> it's very likely that somebody has already created a sensors.conf
> specifically for it. In fact, Tyan distributes (or did for the S2875
> at least) sensors.conf files that /they've/ created for their
> motherboards.
What you will find is that not only do the actual temperature sensors
change from motherboard to motherboard, but also from revision to
revision. Manufacturers do this to cut cost (and boost profit) depending
on the supplier that has the best price for them.
Also, no two sensors are the same. Each sensor is manufactured within a
certain tolerance range, but the readings WILL DIFFER from sensor to
sensor. This means that you WILL need to alter any sensor.conf file you
find with adjustments that fit your specific sensors.
For one motherboard, it might be worth some time to dig through lists
and find someone else with the same sensors on the same revision of your
motherboard, and then fiddle with the adjustments to get a general sense
of the health of your machine.
For a farm of servers, I've long since given up hope of ever maintaining
sensor.conf files. Stability and difficulty of probing chipsets aside,
it is madness to even attempt.
The Large Scale Administration ideal is to architect your apps to scale
horizontally across servers and put a load balancer in front to take out
nodes that die. When one dies (which likelihood statistically increases
the number of machines in your cluster), you simply replace the dead
commodity hardware. Monitor the datacenter environment, watch the system
logs, probe what you can across the farm (SMART values, for example),
and try to manage the farm as homogenous replacable nodes.
- Ian C. Blenke <ian@blenke.com> <icblenke@nks.net> http://ian.blenke.com/
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:59:11 EDT