topic Re: check process in Operating System - HP-UX

check process

hangyu — Wed, 21 Sep 2005 01:00:16 GMT

i have a script that read a file which contains process_id and time that he's
in and it lookes like this
0:30 54545
0:44 66788
0:50 23233
i need to read every line in the file and get the time and if the process is greater then 0:30 to kill the process id
the script looks like this
cat bbb | while read line
do
#kill -9 $i
done
i don't how to take of the hour , ask about it and kill the process
can you please help me and another question
did i do the loop ok did i need the pipe before the while

Re: check process

Vibhor Kumar Agarwal — Wed, 21 Sep 2005 01:10:28 GMT

I think you got the most of it.

cat bbb | while read line
do
awk '{ if ($1<30) print kill -9 $2 }' | sh
done

Re: check process

Muthukumar_5 — Wed, 21 Sep 2005 01:16:44 GMT

Use this:

while read time pid
do

sec=$(echo $time | cut -d":" -f1)

[[ $sec -gt 30 ]] && kill -9 $pid

done <

hth.

Re: check process

Muthukumar_5 — Wed, 21 Sep 2005 01:21:00 GMT

Use simply as,

# awk '{ split($1,a,":"); if ( a[2] > 30 ) { print "kill -9 " $2 } }' | ksh

hth.

Re: check process

Muthukumar_5 — Wed, 21 Sep 2005 01:27:29 GMT

With perl scripting, you don't need reverse shell execution as,

perl -ne '($time,$pid)=split; @min=split(/:/,$time); kill 9,$pid if $min[1] > 30;'

hth.

Re: check process

hangyu — Wed, 21 Sep 2005 01:40:21 GMT

thx Muthukumar ,

I use your script , but I tried to echo the $sec , all sec are "0" ( it should be 30 , 44 , 50 ) , so no one record greater than 30 , could suggest what is wrong ? thx

while read time pid
do

sec=$(echo $time | cut -d":" -f1)

[[ $sec -gt 30 ]] && kill -9 $pid

done <

hth.

Re: check process

Vibhor Kumar Agarwal — Wed, 21 Sep 2005 01:42:57 GMT

I think it will be -f2

Re: check process

hangyu — Wed, 21 Sep 2005 02:02:10 GMT

thx replies ,

it works now , it I want to script to check the process 3 times in very 1 minutes , the crontab job only can run 1 time in 1 minute , could suggest what can I do ? thx

Re: check process

hangyu — Wed, 21 Sep 2005 02:05:11 GMT

or if I want the job run repeatedly , could suggest what can I do ? thx

Re: check process

Orhan Biyiklioglu — Wed, 21 Sep 2005 02:07:53 GMT

while true
do

while read time pid
do

sec=$(echo $time | cut -d":" -f2)

[[ $sec -gt 30 ]] && kill -9 $pid

done <

sleep 20

done

this will run in an infinite loop until you interrupt it.

Re: check process

hangyu — Wed, 21 Sep 2005 03:14:26 GMT

thx reply ,

the process can run repeatedly now , but if I add it to the cron , the process will run many many times , so I think it can't be add to the crontab , could suggest if not add to the crontab , how to make sure the job is keep on running ? thx.

Re: check process

Muthukumar_5 — Wed, 21 Sep 2005 03:25:31 GMT

You can automate this script execution with crontab, at (schedulars) or with scripting running infintite.

#!/bin/ksh
# psck.ksh
while [ TRUE ]
while read time pid
do

ps -ef | grep -q $pid |grep -v grep
if [[ $? -eq 0 ]]
then
sec=$(echo $time | cut -d":" -f1)
[[ $sec -gt 30 ]] && kill -9 $pid
echo "$pid is killed @ $(date)" >>/tmp/logfile
fi

done <

sleep 60
done
# end

Run this script as,

# chmod +x psck.ksh
# ./psck.ksh &

# tail -f /tmp/logfile give details of process which killed.

hth.

Re: check process

hangyu — Wed, 21 Sep 2005 03:46:31 GMT

your explaination is very detail , but I am not too understand how to make sure the script is running in the system if not add it to the crontab ? thx

Re: check process

Vibhor Kumar Agarwal — Wed, 21 Sep 2005 05:34:43 GMT

You require a script to run 3 times every minute, Righto

So make a loop in that script which runs 3 times.
Now add that script in cron scheduled for every minute.

Re: check process

Bill Hassell — Wed, 21 Sep 2005 08:04:04 GMT

As mentioned, cron is limited to one minute resolution. So inside your script, either create a function that performs the kill and then sleep 20 (20 seconds) and repeat two more times, or just code the kill test 3 times with a sleep between each section.

By the way: are you sure you want to use kill -9? It is a very bad command to use against programs, especially databases and other applications that use shared application resources. It is strongly recommended that you use kill -15, followed by a kill -1 (if kill -15 doesn't work) and finally kill -9 as a last resort.