public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: heat codes
Date: Fri, 27 Feb 2015 05:40:36 +0000	[thread overview]
Message-ID: <1706314.sYAyZtBLFs@wstn> (raw)
In-Reply-To: <54EFCCD6.9050604@gmail.com>

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 <host>

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.



  reply	other threads:[~2015-02-27  5:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 18:53 [gentoo-user] heat codes James
2015-02-26 20:13 ` [gentoo-user] " James
2015-02-26 23:02   ` Volker Armin Hemmann
2015-02-27  1:23     ` James
2015-02-27  6:27       ` Volker Armin Hemmann
2015-02-28 11:33   ` Mick
2015-03-12 23:53     ` James
2015-03-13  0:38       ` Dale
2015-03-13  6:20         ` Mick
2015-03-13 11:23           ` Dale
2015-03-13  9:13         ` Peter Humphrey
2015-03-13 11:27           ` Dale
2015-03-13 12:06             ` Peter Humphrey
2015-03-13 15:49               ` Dale
2015-03-13 16:10                 ` Mick
2015-02-26 23:26 ` [gentoo-user] " Dale
2015-02-27  1:31   ` [gentoo-user] " James
2015-02-27  1:48     ` Dale
2015-02-27  5:40       ` Peter Humphrey [this message]
2015-02-27  8:27         ` Dale
2015-02-27  9:02           ` Neil Bothwick
2015-02-27  9:43             ` Peter Humphrey
2015-02-27 20:41               ` wabenbau
2015-02-28  9:48                 ` Peter Humphrey
2015-03-12 19:40                   ` Dale
2015-03-12 22:38                     ` Peter Humphrey
2015-03-12 23:12                       ` Neil Bothwick
2015-03-12 23:29                     ` wabenbau
2015-03-12 23:35                       ` Dale
2015-03-13  5:23                         ` Tuomo Hartikainen
2015-03-13 11:31                           ` Dale
2015-02-27  9:57             ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1706314.sYAyZtBLFs@wstn \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox