05-14-2013
Published online specs...
Saw where it said the operating range is 41 to 104 degrees F.
However, I would never recommend anything outside 60 to 80. When you get up into the 90's, very easy to have components well in the 100's due to poor circulation issues and/or simply some components get hotter and stay hotter longer.
This User Gave Thanks to joeyg For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
As Subject.
thanks. (3 Replies)
Discussion started by: beggar_hong
3 Replies
2. Solaris
Hi all,
We are getting CPU warning temeratures sometimes and our server is shutdown at 80 degree F. We notice our server room temperature at 18 degree celcius . Our we have already cleaned dust from grills near CPU Fan . CPU fans are working (moving) . It is our experience that CPU... (5 Replies)
Discussion started by: Hitesh Shah
5 Replies
3. Solaris
Hi all,
Can any one please tell me how to find these in Unix (Commands)
1. Too many processes connected to the server.
2. High Utilization of CPU.
3. Maximum Number of connections with the database.
OS: Sun Solaris 5.8
DB : Oracle 10g
Thanks and Regards,
Prashanth (1 Reply)
Discussion started by: prashanth_gs
1 Replies
4. 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
5. UNIX for Dummies Questions & Answers
I'm trying to iterate a UNIX awk script that returns min/max temperature data for each day from a monthly weather data file (01_weath.dat). The temperature data is held in $5. The temps are reported each minute so each day contains 1440 temperature enteries. The below code has gotten me as far as... (5 Replies)
Discussion started by: jgourley
5 Replies
6. Solaris
Hi,
I have a NETRA 240 server wich should work on high temperature environment (up to 50 deg celsius). After reaching ~48 deg, the system is shuting down.
The HighShutDownThreshold of the CPU is set to 89 deg
The PowerOffThreshold of the CPU is set to 96 deg
Please help me to change these... (2 Replies)
Discussion started by: Danielz
2 Replies
7. 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
8. Solaris
Hello all,
I am using prtdiag -v command to find the temperature sensors . And i dont see the following o/p .
ystem Configuration: Hewlett-Packard HP Z400 Workstation
BIOS Configuration: Hewlett-Packard 786G3 v01.17 08/19/2009
==== Processor Sockets ====================================
... (2 Replies)
Discussion started by: b.preeya22
2 Replies
9. AIX
I have a system with the following settings:
min:0.10
Assigned: 2.0
Max: 6.0
Partition is uncapped weight is 128.
I would like to know if even if this is uncapped, is the max it can use 6?
The actual pool has 16.
I remember reading about this somewhere but I don't remember can anyone... (3 Replies)
Discussion started by: techy1
3 Replies
10. AIX
Hi All,
Anyone know how to capture the nmon avg and max cpu and memory for one of the AIX server for Monthly Utilization Report purposes ?
Thanks.
---------- Post updated at 05:18 AM ---------- Previous update was at 05:07 AM ----------
if possible use shell script to count or sum... (6 Replies)
Discussion started by: ckwan
6 Replies
LEARN ABOUT HPUX
xmdirection
XmDirection(library call) XmDirection(library call)
NAME
XmDirection -- Data type for the direction of widget components
SYNOPSIS
#include <Xm/Xm.h>
DESCRIPTION
XmDirection is the data type specifying the direction in which the system displays subwidgets, children of widgets, or other visual compo-
nents that are to be laid out. This data type also affects traversal order within tab groups.
XmDirection is implemented as an unsigned char bit mask. The horizontal and vertical directions can be specified independent of each
other. XmDirection also specifies the precedence of the horizontal and vertical directions relative to each other. For example, a value of
XmRIGHT_TO_LEFT_TOP_TO_BOTTOM lays out a component horizontally from right to left first, then vertically top to bottom.
XmDirection provides the following masks, each of which corresponds to a particular bit in XmDirection:
o XmRIGHT_TO_LEFT_MASK
o XmLEFT_TO_RIGHT_MASK
o XmTOP_TO_BOTTOM_MASK
o XmBOTTOM_TO_TOP_MASK
o XmPRECEDENCE_HORIZ_MASK
o XmPRECEDENCE_VERT_MASK
In addition to the preceding single bit masks, XmDirection also provides the following multiple bit masks. These multiple bit masks are
particularly useful as arguments to XmDirectionMatchPartial:
o XmHORIZONTAL_MASK
o XmPRECEDENCE_MASK
o XmVERTICAL_MASK
Motif also provides the following enumerated constants for specifying various combinations of directions:
XmRIGHT_TO_LEFT_TOP_TO_BOTTOM
Specifies that the components are laid out from right to left first, then top to bottom.
XmLEFT_TO_RIGHT_TOP_TO_BOTTOM
Specifies that the components are laid out from left to right first, then top to bottom.
XmRIGHT_TO_LEFT_BOTTOM_TO_TOP
Specifies that the components are laid out from right to left first, then bottom to top.
XmLEFT_TO_RIGHT_BOTTOM_TO_TOP
Specifies that the components are laid out from left to right first, then bottom to top.
XmTOP_TO_BOTTOM_RIGHT_TO_LEFT
Specifies that the components are laid out from top to bottom first, then right to left.
XmTOP_TO_BOTTOM_LEFT_TO_RIGHT
Specifies that the components are laid out from top to bottom first, then left to right.
XmBOTTOM_TO_TOP_RIGHT_TO_LEFT
Specifies that the components are laid out from bottom to top first, then right to left.
XmBOTTOM_TO_TOP_LEFT_TO_RIGHT
Specifies that the components are laid out from bottom to top first, then left to right.
XmTOP_TO_BOTTOM
Specifies that the components are laid out from top to bottom. If horizontal direction is important, do not use this constant.
XmBOTTOM_TO_TOP
Specifies that the components are laid out from bottom to top. If horizontal direction is important, do not use this constant.
XmDEFAULT_DIRECTION
Specifies that the components are laid out according to the default direction. (This constant is primarily for widget writers.)
XmLEFT_TO_RIGHT
Specifies that the components are laid out from left to right. If vertical direction is important, do not use this constant.
XmRIGHT_TO_LEFT
Specifies that the components are laid out from right to left. If vertical direction is important, do not use this constant.
RELATED
XmDirectionMatch(3), XmDirectionMatchPartial(3), XmDirectionToStringDirection(3), XmString(3), XmStringDirection(3), and XmStringDirection-
ToDirection(3).
XmDirection(library call)