Shell script to monitor process with high CPU

10 More Discussions You Might Find Interesting

1. AIX

Process lose its parent then consume high CPU usage ...

Hello. In an informix context, on AIX 5.3 TL 12, we encounter this problem : Sometimes in the day (probably when users exits from their session), a child process lose its parent (PPID is now "1") and this child is consumming lot of CPU "USER". I tried, on different cases, "truss -p...

2. 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...

3. Shell Programming and Scripting

Restart debian server if one specific process has more than 10 seconds have high cpu load

Hi, could someone give me an example for a debian server script? I need to check a process if the process has a high cpu load (top). If yes the whole server needs to reboot. Thats it, nothing more. ;) Hope someone could help me. Regards woisch

4. UNIX for Advanced & Expert Users

Shell script to monitor cpu and VMstat, iostat

Hi , I am new to scripting. please help me out how to write a script to monitor cpu , vmstat, iostat in Redhat linux. we are doing the load test. Thanks in advance !!!!

5. Shell Programming and Scripting

Need help on shell script to monitor each user cpu use on a cluster over time

Hi, I am relatively new to the cluster administration and shell scripting. I need help on a shell script which can help me determine how many cpu's over time, any particular ( or all registered users on a cluster ) are using. To generate data say over a period of week and list of users and their...

6. Shell Programming and Scripting

Looking for shell script to monitor CPU utilization and send mail once exceed 75%

Dear Group, I'm look for shell script to Monitor CPU usage and send mail once it exceed 75% I'm running Suse10.4.

7. Shell Programming and Scripting

Cron job and shell script to kill a process if memory gets to high

Hello, I'd like to set a cron job that runs a shell script every 30 minutes or so to restart a java based service if the memory gets above 80%. Any advice on how to do this? Thanks in advance! - Ryan

8. Shell Programming and Scripting

script to check high cpu utilization for java process

Hello Team, I need help in preparing script to check for high cpu utilisation for java process. I have many java process on my system which consumes high cpu so i have to monitor it using script. ---------- Post updated 12-10-10 at 02:21 AM ---------- Previous update was 12-09-10 at...

9. AIX

High CPU utilization by a pro*C process

Hi , we upgarded our AIX from 5.3 to 6.1 and upgraded our xlc compiler from ver 6.0 to 9.0 . After this upgrade one of our pro*C program is utilizing around 20% of the CPU. Before upgarde its using only 0.2 %. when i try to debug using the truss command i got the below error. $...

10. Programming

how to monitor the child process on which cpu core

Hi all. Sorry to express my questions wrongly in my early post,I repost my question again here. My pc has dual core, I wirte an application with two process, parents process and child process. My quetion is how to realize :if the child process is on core 0,it will tell me I'm on core 0,if it...

LEARN ABOUT REDHAT

slabinfo

SLABINFO(5)							   Linux manual 						       SLABINFO(5)

NAME

       /proc/slabinfo - Kernel slab allocator statistics

SYNOPSIS

       cat /proc/slabinfo

DESCRIPTION

       Frequently  used  objects  in  the Linux kernel (buffer heads, inodes, dentries, etc.)  have their own cache. The file /proc/slabinfo gives
       statistics. For example:

	      % cat /proc/slabinfo
	      slabinfo - version: 1.1
	      kmem_cache	    60	   78	 100	2    2	  1
	      blkdev_requests	  5120	 5120	  96  128  128	  1
	      mnt_cache 	    20	   40	  96	1    1	  1
	      inode_cache	  7005	14792	 480 1598 1849	  1
	      dentry_cache	  5469	 5880	 128  183  196	  1
	      filp		   726	  760	  96   19   19	  1
	      buffer_head	 67131	71240	  96 1776 1781	  1
	      vm_area_struct	  1204	 1652	  64   23   28	  1
	      ...
	      size-8192 	     1	   17	8192	1   17	  2
	      size-4096 	    41	   73	4096   41   73	  1
	      ...

       For each slab cache, the cache name, the number of currently active objects, the total number of available objects, the size of each object
       in  bytes,  the	number of pages with at least one active object, the total number of allocated pages, and the number of pages per slab are
       given.

       Note that because of object alignment and slab cache overhead, objects are not normally packed tightly into pages.  Pages with even one in-
       use object are considered in-use and cannot be freed.

       Kernels	compiled with slab cache statistics will also have "(statistics)" in the first line of output, and will have 5 additional columns,
       namely: the high water mark of active objects; the number of times objects have been allocated; the number of times  the  cache	has  grown
       (new  pages  added  to this cache); the number of times the cache has been reaped (unused pages removed from this cache); and the number of
       times there was an error allocating new pages to this cache.  If slab cache statistics are not enabled for this kernel, these columns  will
       not be shown.

       SMP  systems  will  also  have  "(SMP)" in the first line of output, and will have two additional columns for each slab, reporting the slab
       allocation policy for the CPU-local cache (to reduce the need for inter-CPU synchronization when allocating objects from the  cache).   The
       first  column  is  the per-CPU limit: the maximum number of objects that will be cached for each CPU.  The second column is the batchcount:
       the maximum number of free objects in the global cache that will be transferred to the per-CPU cache if it  is  empty,  or  the	number	of
       objects to be returned to the global cache if the per-CPU cache is full.

       If  both  slab  cache  statistics  and SMP are defined, there will be four additional columns, reporting the per-CPU cache statistics.  The
       first two are the per-CPU cache allocation hit and miss counts: the number of times an object was or was not available in the per-CPU cache
       for  allocation.   The  next  two are the per-CPU cache free hit and miss counts: the number of times a freed object could or could not fit
       within the per-CPU cache limit, before flushing objects to the global cache.

       It is possible to tune the SMP per-CPU slab cache limit and batchcount via:

       echo "cache_name limit batchcount" > /proc/slabinfo

AVAILABILITY

       /proc/slabinfo exists since Linux 2.1.23.  SMP per-CPU caches exist since Linux 2.4.0-test3.

FILES

       <linux/slab.h>

								    2001-06-19							       SLABINFO(5)

Shell Programming and Scripting