From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 36393138ACE for ; Fri, 27 Feb 2015 05:40:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 41FF7E0950; Fri, 27 Feb 2015 05:40:39 +0000 (UTC) Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7]) by pigeon.gentoo.org (Postfix) with ESMTP id 3896FE093D for ; Fri, 27 Feb 2015 05:40:38 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01d.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YRDfB-000CdI-CY for gentoo-user@lists.gentoo.org; Fri, 27 Feb 2015 05:40:37 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: heat codes Date: Fri, 27 Feb 2015 05:40:36 +0000 Message-ID: <1706314.sYAyZtBLFs@wstn> Organization: Society for Retired Gentlefolk User-Agent: KMail/4.14.3 (Linux/3.17.8-gentoo-r1; KDE/4.14.3; x86_64; ; ) In-Reply-To: <54EFCCD6.9050604@gmail.com> References: <54EFCCD6.9050604@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01d-IP: [82.69.80.10] X-Archives-Salt: 04d3a694-b3e7-425e-a07b-5135380db77a X-Archives-Hash: 3e69c512bb3d30d89fe0025c72cdfe67 On Thursday 26 February 2015 19:48:06 Dale wrote: > While it has been a while since I used gkrellm to monitor a remote > system, I use it every day to monitor my system I sit at. Keep in > mind, not much changes on how gkrellm works. It looks for > temp/fan/CPU/memory etc info and displays it. I'm not sure it > requires a whole lot of updating to do that especially given it has > worked fine here for ages and not much has really changed. Yes, I have two instances of it running permanently too. Though I think James is right too, in that it does still have the odd bug. > It was the remote part that I wasn't sure about. I know it used to > have that feature and if it still does, the remote part works just > like the local part does. You just tell it to monitor something > other than the system you are sitting at. $ gkrellm -s Then set it up the same way as you would the local one. KDE even knows to restart it along with other progs, which is more than can be said for Chromium. -- Rgds Peter.