From owner-freebsd-questions@freebsd.org Sat Jul 4 17:38:33 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 24FF29B5F for ; Sat, 4 Jul 2015 17:38:33 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01C6F1870 for ; Sat, 4 Jul 2015 17:38:32 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id A40113F734 for ; Sat, 4 Jul 2015 13:38:30 -0400 (EDT) Message-ID: <55981A11.8090300@sneakertech.com> Date: Sat, 04 Jul 2015 13:38:25 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Best console hardware monitor pkg? References: <559760A3.7000901@sneakertech.com> <20150704150742.cd7c045a.freebsd@edvax.de> <20150704092041.03767068@seibercom.net> <5597F233.7090201@sneakertech.com> <20150704170548.fc12bd39.freebsd@edvax.de> <20150704161736.7025b3e187c9efbe119b1cc6@sohara.org> <5597FACB.3050506@sneakertech.com> <5597FBCD.2060001@hiwaay.net> <55980239.9010601@sneakertech.com> <20150704180726.b46748f7.freebsd@edvax.de> In-Reply-To: <20150704180726.b46748f7.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 17:38:33 -0000 > It would probably have made more sense to call the combined > package simply mbmon, with a "make configure" step if you > wanted it with X support - which means that the list of > runtime dependencies would grow. The "x" in "xmobon" package > naming therefore is a bit confusing, as it refers to the > option of X support, not a default X support... Hmm.... ok, well I guess as long as it's deliberate it's probably ok. > To expand a bit, mbmon & healthd seem to agree on (chipset ?) temp, as > distinct from amdtemp. However both only report for 2 CPU's (cores ?), > while amdtemp reports (wrongly, IMHO) for all 4 (in my case) .... If > healthd &/or mbmon would report (accurately) for all 4 cores, I'd love > them more :-) .... Maybe mbmon and healthd are confused about hyperthreading and think you only have two real cores? That's the only thing I can think of.