topic Re: shell programing in Operating System - HP-UX

shell programing

TOMAS BERNABEU — Fri, 28 Jun 2002 07:52:29 GMT

As it could detect pid of a process that is called "myprocess" of the user "myuser", who takes more than 24 hours in march and that consumes more of 80% of CPU during 60 minutes?

Thanks !!

Re: shell programing

Olav Baadsvik — Fri, 28 Jun 2002 08:18:37 GMT

Hi,

Not quite clear to me what you are after.
I think you will have to explain a bit
more what your problem is.

Regards
Olav

Re: shell programing

Peter Kloetgen — Fri, 28 Jun 2002 09:38:31 GMT

Hi Tomas,

Your description sounds like you need simply a software product which allready exists:

lsof

You can download it here:

javascript&colon;openExternal('http://gatekeep.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.61/')

Allways stay on the bright side of life!

Peter

Re: shell programing

Shahul — Fri, 28 Jun 2002 11:49:44 GMT

Hi

What I understood from ur question is, U wnat to get PID and user of the processes which are using more 80% of the CPU...Right?
The following script will list the processes which are using above 80% CPU. U can shrink or customize as per ur requirement.

ps -ef |sed '1d'>pall;awk '{print $4}'pcpu
for i in `cat pcpu`
do
if [ "$i" -gt 80 ];then
line fi;sed '1d' pall>pallout;mv pallout pall
done

Best of luck
Shahul

Re: shell programing

David Totsch — Tue, 02 Jul 2002 15:15:16 GMT

Tomas:

MeasureWare is great for alarming on misbehaving processes. If you have the MeasureWare collection daemon scopeux running, you could place an alarm in /var/opt/perf/alarmdef that can run a progam when a process exceeds the thresholds you write into the alarm. You can find examples in /opt/perf/examples. You can loop through per-process data scanning for processes that have PROC_CPU_TOTAL_UTIL greater than 80% for 60 minutes. If you do not have GlancePlus Pak, you can install trial software from your application CDs to give it a whirl.

Just keep in mind that alarming on a process running for more than 24 hours may be a little difficult (you would have to specify accumulated CPU time instead of linear start/stop times). Maybe PROC_CPU_TOTAL_TIME_CUM greater than 86400 seconds (24hours of execute time -- you might want a smaller number).

-dlt-