09-21-2018
Hi,
I'd just included that as a demonstration of how if works, really, so you could get an idea of what you need to do in your own code. So rather than directly using my example script, you'd adapt it and write your own if statement in your script to test the value of your temperature variable, after your script had set it.
So looking at your provided code, your could write an if statement at the end to test the value of the tc variable (assuming that's correct, and it does contain just a single integer that is the number you want to test). If the variable tc isnt' the right one then you'd use whatever variable contains the CPU temperature as an integer, and do the if tests on that.
If that doesn't work then if you can provide an example of the code you've written and what goes wrong when you run it, I'd be happy to help further in debugging and we can take things from there.
9 More Discussions You Might Find Interesting
1. HP-UX
I'm fairly new to hpux, so this is what i've been trying to figure out. Is it possible to get any logs on hpux that would indicate if the system, cpu, or other hardware components reached above normal or critical temperatures?
Thanks,
-K (0 Replies)
Discussion started by: uzerx
0 Replies
2. SCO
Is there command in sco unixware 7.1.3 from which i can find the temperature of the system/hardware.
Something equivalent to prtdiag in solaris maybe
thanks (1 Reply)
Discussion started by: gsb81
1 Replies
3. Solaris
Hi all
I have a SUN V480 server with 4 processores and I've noticed that the temperature for 2 of the 4 processers are quite high (63 degrees Celsius).
Does anyone know what the operating temperatures of the Sparc CPU's are? I'm not getting any warning messages yet, but I want to resolve the... (3 Replies)
Discussion started by: soliberus
3 Replies
4. Filesystems, Disks and Memory
Hi,
I just set up a raid Z array in solaris xpress and I notice that the drives feel pretty damn hot. I use speedfan to monitor the temperatures of the hard drives in XP. Is there a similar program for solrais? I assume there would be since the drives all have temp sensors in them, but I... (2 Replies)
Discussion started by: ciscocbee
2 Replies
5. Shell Programming and Scripting
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Discussion started by: Max89
1 Replies
6. Solaris
How to get a CPU temperature and current power consumption in T5220 server both from system controller and Operating system. I need details by cores. Thanks in advance. (13 Replies)
Discussion started by: fugitive
13 Replies
7. UNIX for Dummies Questions & Answers
People hello to everybody exist a way to do a script for view the temperature. I have
Red Hat Linux release 9 (Shrike)
Kernel 2.4.20-8 on an i686
THANk YOU FOR YOUR TIME. (4 Replies)
Discussion started by: enkei17
4 Replies
8. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
9. Solaris
some say '/usr/sfw/bin/ipmitool' can be used to read temperature. has anyone tried it? what options should be used? (1 Reply)
Discussion started by: orange47
1 Replies
LEARN ABOUT DEBIAN
openscad-testrun
OPENSCAD-TESTRUN(1) General Commands Manual OPENSCAD-TESTRUN(1)
NAME
openscad-testrun - set up and run the OpenSCAD test suite
SYNOPSIS
openscad-testrun [options]
DESCRIPTION
This manual page documents briefly the openscad-testrun command.
openscad-testrun is a script that sets up a directory in which the OpenSCAD test suite (implemented in ctest) can be run by creating sym-
links to the system locations of the input data, and runs it. The created directory is not removed, but will contain the test results in
addition to the symlinks.
It is required as the test suite in its original form expects all the test input and output data in relative locations, and the typical
user has no write access to where the data resides. Future changes to the test suite might make it more flexible, removing the need for
this script.
OPTIONS
-d directory, --directory directory
Set up the tests in a directory called directory. By default, this is generated from the current date and time like openscad-
test-2012-02-15_13:37.
-n, --dry-run
Do not run the test suite, just set it up.
All additional arguments are passed on to ctest.
AUTHOR
The OpenSCAD test suite was written by Clifford Wolf, Marius Kintel, and others. The openscad-testrun script was written by chrysn.
This manual page was written by chrysn <chrysn@fsfe.org>, for the Debian project (and may be used by others).
2012-02-16 OPENSCAD-TESTRUN(1)