Sponsored Content
Top Forums Shell Programming and Scripting System Health - Cpu, Load, IO Monitor Post 302475704 by SkySmart on Monday 29th of November 2010 03:05:12 PM
Old 11-29-2010
System Health - Cpu, Load, IO Monitor

hello there,

can someone please tell me the commands that makes sense, from a production point of view, to be used to make sure CPU, LOAD or IO usages on a Linux or Solaris server isn't too high?

I'm aware of vmstat, iostat, sar. But i seriously need real world advice as to what fields in the output of these commands (or others if there are), that I need to look at and compute on.

Please advise.

thanks
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

load monitor script

I need help in finding a script to monitor loads for 8+ servers on a single console. The goal here is to centralize it and run the script from a single server. Can anyone help on this? Im running this script on each server to monitor the load. while true; do w | grep average | grep -v grep... (7 Replies)
Discussion started by: locabuilt
7 Replies

2. Solaris

Multi CPU Solaris system shows 100% CPU usage.

Hello Friends, On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization. ========================================================================= $ prstat -a ... (4 Replies)
Discussion started by: mahive
4 Replies

3. Solaris

Monitor server's health

Dear all, There wasn't any monitoring on our server except on the filesystem. Therefore, I was wondering anything i should do on a daily basis to check on the server's status, health, hardware, or any other thing as a disaster prevention? Also, what command i should use to do that? ... (2 Replies)
Discussion started by: beginningDBA
2 Replies

4. Shell Programming and Scripting

Script to monitor Machine Health (Project Doctortux) Input needed.

I have written little script to check the CPU performance of the machine. Request you to contribute your comments on the same. Feel free to add your own scriptlet to make it better. I have decided to call it as doctortux I have decided to run the script in two mode 1)Interactive.(Not... (4 Replies)
Discussion started by: pinga123
4 Replies

5. Shell Programming and Scripting

Monitor the CPU load for each process and total

Hi guys, I have to set up a script which monitors the amount of AVG CPU load per each process and also the total load for a sum of processes. The processes have the same name, I can only differentiate by port number they listen to, as follows : 28171 root 20 0 1089m 21m 3608 S 103... (1 Reply)
Discussion started by: liviusbr
1 Replies

6. Solaris

Best way to monitor health of Solaris zones ?

What is the best way to monitor the health of solaris zones? Through the global zone or through the individual zones itself ? (5 Replies)
Discussion started by: CuriousDev
5 Replies

7. UNIX for Beginners Questions & Answers

Top 5 cpu and Mem consuming process and files and suggestion for health check

I am middle of writing health check scripts, can you pls share commands on how I can get cpu and Mem of top consuming process info at the moment? Also can u suggest ideas on what all I can look for as a part do health check on red hat Linux server? I searched on site before posting, but... (2 Replies)
Discussion started by: Varja
2 Replies
lafe(6) 							   Games Manual 							   lafe(6)

NAME
lafe - Latency Free Empire client SYNOPSIS
lafe country [password [host [port]]] DESCRIPTION
lafe is an empire client optimized for high latency links. You can type in, edit, and send several commands before the server replies with output from the first command. This allows you to make better use of the existing bandwidth than most other clients. pei and eif are par- ticularly susceptible to latency, as they require a complete exchange of data before prompting again. lafe could also be called LAg Free Empire. Empire 2 asynch features are supported. Empire 3 C_SYNC isn't supported, as this is a rather dumb client (in between emp_client and eif) and C_SYNC was removed from Empire 4 (Wolfpack). Readline is supported, and at the moment required. If you want lafe without readline, use emp_client instead. Parameters country If the only parameter this is use as a key to look up the game name as specified by the addgame commands in the $HOME/.laferc file. Otherwise it is used as the country name on the server. Defaults to 'visitor' if unspecified. password defaults to 'visitor' if unspecified. host defaults to 149.84.128.9 if unspecified. port defaults to 6667 if unspecified. Local commands help print syntax summary of local commands. addgame game country password host port logfile directory add a game definition for the "lafe game" startup method. execute Handles exec scripts locally runfeed Runs the argument as a shell command, and sends the output to the server shell Run the argument as a shell script alias Print, delete, or define an alias. Use single quotes around the alias definition to protect $*, $1, $2, ... setvar Set, delete, or print local variables. shell Run parameters in a subshell. history print the previous commands. verbose toggle verbosity of message. "verbose on" if you want all the error messages, C_SYNC messages, etc. Off by default. waitsync Wait for all responses from server before proceeding. Useful in scripts before a runfeed or shell command. ENVIRONMENT
Environment variables are supported for backward compatibility with emp_client. This information is best placed in the $HOME/.laferc file using the addgame command. EMPIREHOST hostname of server EMPIREPORT TCP/IP port number of server COUNTRY Country name to log in as REPRESENTATIVE Password for country FILES
$HOME/.laferc contains any valid local commands to run before connecting to a server. SEE ALSO
emp_server(6), emp_client(6), emp_hub(6), pei(6), eif(6), http://wolfpackempire.com/ BUGS
Output redirection does not work with aliases and internal commands. Simultaneous connection to multiple servers is not yet supported. Version 1.0 addresses both of these issues, but has stalled due to lack of time. When typing well ahead of the server, lafe must guess whether a local command should be parsed locally or forwarded to the server (as part of a telegram for instance). It guesses local, which is not always correct. This is the price you pay for speed. AUTHOR
This manual page was written by Drake Diedrich <dld@debian.org> lafe(6)
All times are GMT -4. The time now is 06:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy