11-14-2012
which plateform/OS do you run ?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have a server constantly have high iowait, but i am not able to tell which process generate the most of io. none commands, such as iostat, sar, top will give me this kind of information.
hope there is some command can help me to spot the process generate the most of io
let to know input... (1 Reply)
Discussion started by: giantpanda77
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
Any ideas how to reduce IOWAIT and increase disk speed on Linux server.
Server has 4 CPUs and with 8GB RAM.
Thanks in advance,
Regards,
Bache (3 Replies)
Discussion started by: bache_gowda
3 Replies
3. Linux
Hi all,
Under top command you could see some iowait output.
Is any way to locate which process(s) is causing the high percentage of iowait?
17:48:39 up 19 days, 18:54, 3 users, load average: 3.24, 3.14, 3.17
392 processes: 389 sleeping, 1 running, 2 zombie, 0 stopped
CPU states: cpu user... (3 Replies)
Discussion started by: will_mike
3 Replies
4. Shell Programming and Scripting
Does anyone have a monitoring script in solaris that monitors the drives in an exclosure? The script should be in /bin/bash or /bin/sh thnks again
This should be for solaris 10/11 looking for something that tells me a drive is down or offline.:confused: (0 Replies)
Discussion started by: walnutpony123
0 Replies
5. UNIX for Dummies Questions & Answers
Hi all
Can anyone advise/confirm whether total CPU usage when running sar is %user+%system+%iowait or is it %user+%system only?
I want to confirm whether I am having a CPU-bound problem or not.
This is a single-CPU VMware machine.
$ sar 5 20
Linux 2.6.18-238.5.1.el5... (7 Replies)
Discussion started by: newbie_01
7 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
In a script I would like to check whether the current running command is completed in 1 hour or not. This i want to achieve inside the same script. I don't want to use separate script to monitor my current running script.
eg.
pseudocode;
Command1
if command1>60 mins
then... (7 Replies)
Discussion started by: Vicky5
7 Replies
7. Shell Programming and Scripting
HIi Guys... I am in a fix.... 1st the code :
Script 123.sh looks like this :
./abc # a script which is getting called in this script
while true
do
count=`ps -ef | grep abc | wc -l`
if
echo "abc is running
sleep 10
fi
done
but the process is getting checked... (5 Replies)
Discussion started by: chatwithsaurav
5 Replies
8. Infrastructure Monitoring
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
9. UNIX for Advanced & Expert Users
Hi all,
on our application server we have the following script that monitor the status of the website, my problem here is that i have edite the retries from 3 to 5,
and the timewait to 120 second,
so the script should check 5 times every 2 minutes, and if the fifth check fails it must restart... (0 Replies)
Discussion started by: charli1
0 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1 A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.11 1 Mar 1994 queuedefs(4)