Hello people !
Does anyone knows how can I get the CPU configuration in the RedHat Box ???
I need know the frequence of cpu and how much cpu(s) in my box ...
Thank you,
Witt (2 Replies)
Gurus,
Having a GS1280 box with OSF1 v5.1 installed (16 processors), the run queue value from the vmstat command reports a very high value (about 25 to 30). Does this reflect a CPU bound system. Note that the average CPU utilization is about 60 % which means that the CPU is not that loaded.
Can... (0 Replies)
Hello, everyone.
Could someone, please, tell me how to get the number of bytes in the terminal input queue without blocking and without consuming these bytes? I guess it could be called the peek functionality.
I've looked at termio tcgetattr() and tcsetattr() functions but could not find... (4 Replies)
Hello,
I have to create shell script being myself real novice in scripting...
I was looking on the Internet for some script examples, but I don't have the basic understanding of the shell. I was trying to do something with “ps” command without success.
For exemple total number of... (2 Replies)
Hi
How to display cpu models in Sol 10 ?
Is there some cmds within korn shell or I have to access this info from network
service processor ILOM ?
thx for help (2 Replies)
Hi,
Currently we are experiencing qdaemon died, hourly.
We have more than 10,000 print queue on AIX 5.3.
Would this cause the qdaemon to die?
What is the maximum number of print queue on AIX 5.3?
Thank you in advance. (0 Replies)
Hi Everybody,
Can anybody explain how CPU idle% is about 50%, but runq-sz more than 1?
sar from Solaris 10:
00:00:05 %usr %sys %wio %idle
17:00:08 27 12 0 61
17:20:05 40 15 0 45
17:40:05 27 12 0 61
18:00:05 23... (2 Replies)
root:/>
# lscfg -vp|grep -c -E 'proc.*Processor'
8
root:/>
# lscfg -vpl sysplanar0 | grep -i way
8 WAY PROC CUOD :
8 WAY PROC CUOD :
8 WAY PROC CUOD :
8 WAY PROC CUOD :
8 WAY PROC CUOD :
8 WAY PROC CUOD :
I have this output and need to know how... (3 Replies)
Hello guys,
I am doing a performance analysis on one of our psystem. Most of time I am using Nmon analyser to do my trend graph. But I can't find any help with it. We are interesting in the time spend by tasks in Aix run queue.
After looking the Aix documentation, I am pessimist to find any... (3 Replies)
Discussion started by: GiiGii
3 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE queuedefs(4)