From owner-freebsd-questions@freebsd.org Sat Jul 4 13:27:27 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B96E921F for ; Sat, 4 Jul 2015 13:27:27 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D669104E for ; Sat, 4 Jul 2015 13:27:26 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.1/8.15.1) with ESMTPSA id t64DRC6i096453 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 4 Jul 2015 14:27:13 +0100 (BST) (envelope-from matthew@FreeBSD.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t64DRC6i096453 Authentication-Results: smtp.infracaninophile.co.uk/t64DRC6i096453; dkim=none reason="no signature"; dkim-adsp=none; dkim-atps=neutral X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6] claimed to be liminal.local Message-ID: <5597DF28.50903@FreeBSD.org> Date: Sat, 04 Jul 2015 14:27:04 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Best console hardware monitor pkg? References: <559760A3.7000901@sneakertech.com> In-Reply-To: <559760A3.7000901@sneakertech.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ua5q60U2LcdVV6RW1O0tPnln4XaBpEkk7" X-Virus-Scanned: clamav-milter 0.98.7 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2015 13:27:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ua5q60U2LcdVV6RW1O0tPnln4XaBpEkk7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 04/07/2015 05:27, Quartz wrote: > What's the general opinion these days on the "best" utility for > monitoring all the temperature probes, fan speeds, and other readouts > from a motherboard? (One that doesn't need X and can be installed > through pkg). This depends on exactly what sort of hardware you have. There are different monitoring tools depending on your motherboard and processor. With modern CPUs there is usually an on-die thermal sensor which you can interrogate by loading a kernel module: see coretemp(4) and amdtemp(4) -- using these will let you read out CPU temperature using sysctl(1). Unfortunately access to other monitoring variables is less consistent. Probably your best bet is if you've a server class motherboard with some sort of lights-out management capability -- or indeed many other motherboards nowadays. In which case you should be able to load the ipmi(4) kernel module and install ipmitool(8) from ports to be able to query it. Using IPMI enables you to get, and possibly set, a lot of the stuff that's usually only accessible from the system bios, as well as access to on-board temperature sensors, PSU voltages, chassis intrusion sensors and fan speeds. Now, while the tool and the management interface is common to a lot of different manufacturers, exactly how the monitoring data is structured is not, so it might take a bit of shell scripting to massage the data into a usable form. Cheers, Matthew --ua5q60U2LcdVV6RW1O0tPnln4XaBpEkk7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQJ8BAEBCgBmBQJVl98vXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATwlIQAJGpjUDNRlXhjGWmQSn0y2JA WgJZgSsV2t2P11SqfHF0dZ2hafY6fcszYT2OQmA1OVhPWZ+fpFDbcX7fDNlQkMP9 EbtQYMZFBDFYbBCO5hbiFuG29p4zfkbeCL5iiydw2k1Pu4V+4l3GrhLcn1t7Zd/Z VEx4a3bC92NtNBSLoAEIBWlC48jenDsVUEI2srG+xb3Xq7w0hSV4aRJiotJ5iysi job3hBsUUPO3LTSbPAgNzhs9WXtzYGG2xYH4bcCE6VdblMWaiYnlFZM3Q6j018hq wEuniDSvMHFS7XaFPkVkdmz9NhIiQj/A2vAZqQcEavzY8EUlQXBV+oD+dosfOKPf vcY8FmK/0CtLA/UCLbjJ7HJiqKnUIHXFw0WAuF/7PZmUraU5kvdB+rvD+H1Ao4Wu iRu+8vv78RhS5JG5DX4rffdrLkUMz/TFvD+kl1Y6Xo8wc7UyF2p1momJpGhvnc3y gx/FKIUGZxbLZ4f+Mebhk2ROIycTTYgd0rIVvjGlGE2MUnH7pvds+hhPMQ/p5/5F 6wHq/AO1YGiXpJI5GLbtL/NdwcgOx8whgIIS1jYGB+M6/iWbZHK5zH5ci1a1hkQR Wvw/V8akGXmDBdzYmTAgV/jNMAZSWmyu1ImGnYhhbRWmxEf0vyDxSqiTvFtaznaT Og0sdkbImsadFy4AD/5G =FKph -----END PGP SIGNATURE----- --ua5q60U2LcdVV6RW1O0tPnln4XaBpEkk7--