To: 9fans <email@example.com>
Subject: Re: [9fans] cpu temp in drawterm
Date: Tue, 14 Feb 2023 17:13:39 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
Resending this through the web interface because my email was dropped.
Temperature stats are read from /dev/cputemp. How that file is served depends on your system.
On my machine the file is just in arch(3), other machines use acpi(8) to serve this.
You just need to ensure this file is in the namespace stats(1) is run within.
For getting the temperature of the machine you are connecting to, either:
% bind -a '#P' /dev # if your machine is like mine
% aux/acpi # if your machine uses acpi
You will likely have more success in just cracking open the code and reading it then you will with google.
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1521 bytes --]
next prev parent reply other threads:[~2023-02-14 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 21:05 jimerickso
2023-02-14 21:28 ` Skip Tavakkolian
2023-02-14 22:04 ` David du Colombier
2023-02-14 22:13 ` moody [this message]
2023-02-14 23:55 ` Jim Erickson
2023-02-15 6:37 ` Skip Tavakkolian
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).