09-22-2010
One quick and dirty way is to measure the amps using a clamp-on amp meter around the power cords.
7 More Discussions You Might Find Interesting
1. HP-UX
Hi All,
Need to find the power consumption of a RX7640 server.
Please help.
Regards,
Sag. (3 Replies)
Discussion started by: sag71155
3 Replies
2. Solaris
We have Sun OS running on spark :
SunOS ciniwnpr67 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V440
Having Physical RAM :
Sol10box # prtconf | grep Mem
Memory size: 8192 Megabytes
My Top Output is :
130 processes: 129 sleeping, 1 on cpu
CPU states: 98.8% idle, 0.2% user, 1.0%... (39 Replies)
Discussion started by: rajwinder
39 Replies
3. Solaris
We have Sun OS running on spark :
SunOS ciniwnpr67 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V440
Having Physical RAM :
Sol10box # prtconf | grep Mem
Memory size: 8192 Megabytes
My Top Output is :
130 processes: 129 sleeping, 1 on cpu
CPU states: 98.8% idle, 0.2% user, 1.0%... (27 Replies)
Discussion started by: rajwinder
27 Replies
4. Shell Programming and Scripting
Inorder to find the user memory consumption I used the command: prstat -s cpu -a -n 10
But now I want to automate it and want to write the output to a file.
How can I write the out put of user name and percentage of consumption alone to an output file.? (2 Replies)
Discussion started by: engineer
2 Replies
5. UNIX for Dummies Questions & Answers
Hi
Is there any native commands or somewhere in the /proc files to get the machine's power consumption? I googled for a while and cannot really find this information
Thanks for your help. (6 Replies)
Discussion started by: flagman5
6 Replies
6. Shell Programming and Scripting
Hi
I'd like to check that a bunch of firewall rules have been applied and, therefore, want to write a script that basically does the following:
telnet serverA port1
telnet serverA port2
telnet serverB port1
telnet serverB port2
I would just compile the list in excel and run it as a... (2 Replies)
Discussion started by: jibberish
2 Replies
7. AIX
Hi,
This thread has been posted before on linuxquestions.org, but no answer, maybe because this is unix question and not linux. I'm posting the same thread here, hope I can get an answer from someone in the meantime, I wish I could post of emergency thread but it needs bits which I don't have :... (6 Replies)
Discussion started by: aLuViAn
6 Replies
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
halt, reboot -- stopping and restarting the system
SYNOPSIS
halt [-lnqu]
reboot [-lnq]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the wtmp(5) file.
When the system is halted with the halt command, the system is powered off.
The options are as follows:
-l The halt or reboot is not recorded in the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SIGTERM TO SIGKILL INTERVAL
The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time. Programs are expected to take only enough time to
flush all dirty data and exit. Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this func-
tionality.
SEE ALSO
wtmp(5), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
June 9, 1993 BSD