![]() ![]() ![]() You'll see periodic logs like the following (I've removed the date and hostname): sensord: Chip: acpitz-virtual-0 That way you can also set up alerts to be notified when things start going wrong.Įxpanding on the sensord example, you can find its output in the system log, with sensord as the process name so either look for sensord in /var/log/syslog (by default), or run journalctl -u sensord. Once you've configured the various tools required to extract temperature information, you'd be better off using a proper monitoring tool (such as Munin) to log the temperatures instead of relying on the system logs. (Most of the systems I've seen have at least one, invalid, monitoring entry which would set off alarms if it was auto-configured!) Of course it's entirely possible to set up an installer image for your own systems since you know what they are and how they're configured. ![]() This configuration requirement means that it would be difficult to set up a generic distribution which logs temperatures by default in a meaningful way. Many other tools can retrieve this type of information (using IPMI, SNMP, etc.) but again in most cases they need to be configured, either to be able to access the information in the first place, or to be able to interpret it, or both. Taking Debian as an example, sensord will periodically log all the information it knows about (system temperatures, voltages etc.) to the system log, but it needs to be configured manually before it can log anything useful hddtemp can be set up to periodically log hard drive temperatures. Most mainstream Linux distributions do include various packages which can log temperatures, and some of these packages are set up to log by default. I'm not aware of a mainstream Linux distribution which logs this type of information by default.
0 Comments
Leave a Reply. |