From: jon.roland@the-spa.com (Jon Roland)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Processes causing CPU to overheat
Date: Tue, 23 Aug 2005 20:27:31 +0000 [thread overview]
Message-ID: <430B2447.6030004@the-spa.com> (raw)
In-Reply-To: <430A5153.2040604@linux-migration.net>
I am trying to write some scripts that would:
1. Sense when the CPU temperature rises above a preset threshold level, and if it
does, launch a program to remedy the condition.
2. The launched program would kill the first process named "perl -w".
3. It would then sleep for some period of time, say 30 seconds, to allow time for
the prelink process to start, which seems to always come after the perl processes,
and which itself threatens an overheat.
4. Kill the prelink process.
Some of the scripts I have written so far:
psk:
kill `ps -ef | grep "$1" | egrep -v grep | awk '{print $2}'`
psu:
ps -ef --colsP0 | grep "$1" | egrep -v grep 2>&1 | tee `date +%y%m%d%H%M`_ps.log
soh (pseudocode):
if [overheat trigger, returns true when CPU temp > 49 C]
then
psk "perl -w"
sleep 30
psk prelink
end
My problem is to figure out how to write that overheat trigger, presumably based
on the sensors command in some way. Is there something already written that would
do that? I have been searching for one and haven't found one yet.
It also appears there are two prelink processes, and it is the second one that
needs to be halted. Only the first perl process needs to be killed, and it is
distinguished by the "-w" flag.
Attached are some diagnostic log files. It is clear that the prelink process is
luanched by anacron, but it is not clear what is launching the perl processes. I
have manually checked the CPU fan and it shows no sign of slowing or stopping when
the overheating condition arises.
-- Jon
----------------------------------------------------------------
Linux Migration Network 7793 Burnet Road #37, Austin, TX 78757
512/374-9585 www.linux-migration.net jroland@linux-migration.net
----------------------------------------------------------------
--
----------------------------------------------------------------
Starflight Corporation 7793 Burnet Road #37, Austin, TX 78757
512/374-9585 www.the-spa.com/jon.roland/ jon.roland@the-spa.com
----------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0508230323_sensors.log
Type: text/x-log
Size: 12967 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050823/3806f365/0508230323_sensors-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 050823_pst.log
Type: text/x-log
Size: 8169 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050823/3806f365/050823_pst-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 050823_psu.log
Type: text/x-log
Size: 1634 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050823/3806f365/050823_psu-0001.bin
next prev parent reply other threads:[~2005-08-23 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 5:28 [lm-sensors] Fw: Processes causing CPU to overheat Jon Roland
2005-08-23 6:27 ` Jon Roland
2005-08-23 6:55 ` Phil Edelbrock
2005-08-23 18:45 ` Craig Sylla
2005-08-23 20:27 ` Jon Roland [this message]
2005-08-24 17:59 ` [lm-sensors] " Jon Roland
2005-08-24 22:48 ` Jon Roland
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=430B2447.6030004@the-spa.com \
--to=jon.roland@the-spa.com \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.