You can write a script that reads a config file with "procname:cputime" tupels, for example
Code:
x:30
y:1440
That means process "x" may run 30 CPU minutes and process "y" may run 1 CPU day.
The script can check every 10 minutes if any of the running processes exceed these limits, warn the user, and finally kill them (the processes ).
This is an interesting idea, but couldn't that easily be circumvented by renaming the process?
How about this: you create a queuing system, which starts the processes. Set the ulimits for users to values so that they have to use the queueing system and cannot start their jobs directly. This queueing system can be configured by a definition file like MadeInGermany mentioned. You set some parameters like RAM usage, CPU usage, etc., upon which the queueing system decides if a job has to be canceled or not.
A similar idea was the start of the VQS (Vienna Queueing System (german)) back then in the late eighties. It was designed to run very big, massively parallel jobs using a large cluster of IBM RS/6000-systems running AIX. The idea was to make big jobs possible but abort them after relatively short time so that the system was free for other jobs. The short time the jobs ran was enough to test and refine them so that you needed the the long-running job classes only for the final run.
Hi all
I need command to give me the utilization for memory and cpu,and how can I know if the utilization ok or no?
for example in hp unix #top
it is give me utilize for cpu and memory and also I can know if utilize ok or no.
thanks (2 Replies)
Hi,
I want to check the CPU and Memory Utilisation in the whole machine (not for a single process). Can someone send me a ready made script which captures all information in a log every 5min??
Thanks,
Ajith (0 Replies)
Hi All,
Does anyone know what the best commands in the UNIX command line are for obtaining this info:
current CPU usage
memory usage
virtual memory usage
preferably with date and time parameters too?
thanks
ocelot (4 Replies)
hi guys
I just want to know how to get the cpu/memory utilization of a running script?
Well i know that I can use the sar command but it shows the whole system's statistics.
Is it possible to get the stats of a single scirpt or a single running service? (6 Replies)
Hello all,
Below what I saw on my solaris 10 box :
$ prstat
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU
PROCESS/NLWP
683 root 4082M 91M run 10 0 41:45:39 96% snmptrapd/1
syslog gives a lot of :
snmptrapd: illegal
data attempted to be added to table nlmLogVariableTable... (0 Replies)
Hi,
Server AIBVRFCC failed POST while booting on 06/28/2009. Server is up, but OS cannot see two CPUs (CPU 0 and CPU 2) and half of the installed system memory (8 GB is physically installed but only 4 GB is seen by OS now).
bld00016:root psrinfo
1 on-line since 06/28/09 05:51:36
3 on-line... (1 Reply)
Dear all,
i am not getting the exact things what i am expecting from
these commands . just clarify this things ,
1. cpu utilization (min)%
2.peak load cpu utilization (max) %
3.cpu utilization(avg)
4. peak disk busy %
5. peak kb read
6.peak kb write
7.free memory
for... (3 Replies)
Is there a command or file I can look at that tells me how much real memory a machine has? A little background. In my shop we run a bunch of java programs, sometimes some of these jobs have config definitions that call for 2G. I would like to know how many I can run before I exhaust rescources. Any... (12 Replies)
Hi ,
We need to get the CPU% and Memory utilization of process by process id.
Is there any way to do get them ?
I tried few commands like top -p <PID> ,
but am getting error "Quitting top: pset <PID> doesn't exist"
also i tried with ps -eo option but am getting error "ps: illegal option --... (1 Reply)
what is the best way to get the memory and cpu usage of a process on any system?
this is relatively simple. however, i'm looking for a unified method that would work on linux, sunos, hpux, aix.
ps -ef | egrep myprocess | awk '{print $4}' ---> there could be several instances of 'myprocess'... (3 Replies)
Discussion started by: SkySmart
3 Replies
LEARN ABOUT OPENDARWIN
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.10 1 Mar 1994 queuedefs(4)
10-21-2015
).