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

user process

ust3 — Wed, 09 Jan 2008 09:21:00 GMT

I hv existing script to generate some pid to a file, the below is the format of the file ,

$vi pid_file
15484
4521

now I would like to have a script to kill all process , I would like to use the command "kill" first , if can't kill it , then use "kill -1" , if still can't then use "kill -3" , if still not then send mail to administrator , can advise what can i write the script ? thx .

Re: user process

Shrikant Lavhate — Wed, 09 Jan 2008 09:33:17 GMT

Here is logic for what you want:

Read file under script and use kill process under case structure with default case to sendmail. Use echo $? to check id process is killed or not and then accordingle proceed.

Re: user process

Roberto Arias — Wed, 09 Jan 2008 09:38:25 GMT

hi ust3:

try this:

if -z pid_file
then
for i in `cat pid_file`
do
kill $i
done
fi
if -z pid_file
then
mailx ....
fi

or this:

kill $(ps -fu |awk {'print $2'})

regards

Re: user process

Jeeshan — Wed, 09 Jan 2008 09:48:36 GMT

first think which process and which user process you want to kill.

Here is a command with arguments which kill all user process at a glance

#ps -ef | awk '{print $1" "$2}' | grep | awk '{print $NF}' | xargs kill

be careful to use this command.

Re: user process

Dennis Handly — Wed, 09 Jan 2008 10:48:46 GMT

Try something like this. Remove echo before kill if happy. Add a "false" after the echo to go to the next step.
for PID in $(< pid_file); do
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi
echo kill $PID
false # remove after script tested
if [ $? -eq 0 ]; then continue; fi
echo kill -INT $PID
if [ $? -eq 0 ]; then continue; fi
echo kill -QUIT $PID
if [ $? -eq 0 ]; then continue; fi
echo mailx -s "Problem killing process" root <Problem killing $PID.
EOF
done

Re: user process

ust3 — Mon, 14 Jan 2008 08:24:11 GMT

thx replies,

I am trying the script
for PID in $(< pid_file); do
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi
echo kill $PID
false # remove after script tested
if [ $? -eq 0 ]; then continue; fi
echo kill -INT $PID
if [ $? -eq 0 ]; then continue; fi
echo kill -QUIT $PID
if [ $? -eq 0 ]; then continue; fi
echo mailx -s "Problem killing process" root <Problem killing $PID.
EOF
done

But I found the process only run the first part

echo $PID
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi

what I want is if the parocess is not killed , then run kill -1 , then kill -3 , if still not , then send me a mail , please help again. thx

Re: user process

Dennis Handly — Mon, 14 Jan 2008 08:52:32 GMT

>But I found the process only run the first part
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi

If it only does this, then that PID doesn't exist.

>what I want is if the process is not killed, ...

That part is there.

Re: user process

ust3 — Mon, 14 Jan 2008 09:30:38 GMT

thx Dennis ,

I tried the script , it try to kill the PID , but if it fail to kill , it pop the message PID is not alive , it works fine , but it seems not try to kill again by kill -1 , it seems the script is stopped at that time , and do not run the rest part of it (eg. if [ $? -eq 0 ]; then continue; fi
echo kill -INT $PID) , can advise what is wrong ? thx

Re: user process

Dennis Handly — Mon, 14 Jan 2008 09:55:57 GMT

>but if it fail to kill, it pop the message PID is not alive

The "kill -0", doesn't kill it, it checks the PID existance.

>but it seems not try to kill again by kill -1, it seems the script is stopped at that time

If the PID isn't there, it does no good to try to kill it.
To prove this, you could add: ps -fu $PID

Re: user process

ust3 — Tue, 15 Jan 2008 05:49:48 GMT

thx dennis,

I have problem to use kill -0 to check the existence of pid , can advise if I want to skip this checking , what I want is to kill the pid by kill -1 first , if can't then kill -2 , then kill -3 , can advise can can I modify it? thx

how to skip the below part from the script
==========================================
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi

Re: user process

Dennis Handly — Tue, 15 Jan 2008 05:54:06 GMT

>can advise if I want to skip this checking

You can just remove this "kill -0 if ... fi" block of code. But you'll get a mail message.

Re: user process

ust3 — Tue, 15 Jan 2008 06:19:41 GMT

thx dennis ,

I am not understand what is the use the that part of script

===========================================
kill $PID 2> /dev/null
if [ $? -eq 0 ]; then continue; fi
===========================================
is it mean ?
if it fail to kill the PID , then its output = 0 , then do next loop kill -INT ?
but in my mind , the logic should be if it is successful kill PID , the output should be = 0 , that should not go to next loop .

Re: user process

Dennis Handly — Tue, 15 Jan 2008 06:35:42 GMT

>I am not understand what is the use the that part of script
kill $PID 2> /dev/null
if [ $? -eq 0 ]; then continue; fi
>if it fail to kill the PID, then its output = 0, then do next loop kill -INT?

If kill works, its exit status is 0 and then it continues to the next iteration of the loop.
(This is goto/break/continue logic, not scummy nested if.)

>the logic should be if it is successful kill PID, the output should be = 0, that should not go to next loop.

It doesn't go to the next kill -INT but does the next PID.

Re: user process

ust3 — Thu, 17 Jan 2008 09:38:54 GMT

thx dennis,

for PID in $(< pid_file); do
kill -0 $PID 2> /dev/null
if [ $? -ne 0 ]; then
echo "PID $PID is not alive"
continue
fi
echo kill $PID
false # remove after script tested
if [ $? -eq 0 ]; then continue; fi
echo kill -INT $PID
if [ $? -eq 0 ]; then continue; fi
echo kill -QUIT $PID
if [ $? -eq 0 ]; then continue; fi
echo mailx -s "Problem killing process" root <Problem killing $PID.
EOF
done

I tried the script , I hve edit the pid_file , some of pid are exist and some are non-exist , but when the script , it shows are pid is not alive .

PID 58745 is not alive
PID 15645 is not alive
PID 87852 is not alive
PID 15645 is not alive
PID 14454 is not alive

while PID 15645 is exist in my system , can advise what is wrong ? thx

Re: user process

ust3 — Thu, 17 Jan 2008 09:46:49 GMT

I tried

kill -0 15645 , the result is "Operation not permitted" .

thx

Re: user process

Dennis Handly — Fri, 18 Jan 2008 03:44:43 GMT

>kill -0 15645, the result is "Operation not permitted"

Something wrong here. I don't get that on HP-UX. You may get "permission denied".
And if these are the same, it means you need to be root to kill that process.

Re: user process

ust3 — Fri, 18 Jan 2008 07:41:26 GMT

thx dennis ,

if use root to kill -0 , it works, I would like to further ask , if there are many process in the file pid_file , some are of process are alive , some are not alive , the script will still kill the process are alive ?

thx

Re: user process

Dennis Handly — Fri, 18 Jan 2008 07:48:43 GMT

>the script will still kill the process are alive?

Yes. But if your file has data from hours and days ago, you might kill the wrong process, because PIDs are eventually reused.

Re: user process

ust3 — Fri, 18 Jan 2008 08:32:28 GMT

thx Dennis ,

Yes. But if your file has data from hours and days ago, you might kill the wrong process, because PIDs are eventually reused -->

I will remove pid_file after it kill the process , the new pid_file will be generated if it is required to kill .

I would like to confirm you whether the logic is :
it first read all pid in pid_file (kill -0) , it try to kill it by "kill" , if successful to kill , then do nothing , if unsuccessful to kill , then try kill -INT , if still not success , then try kill -QUIT , if still not success , then mailx , is the logic correct ? thx

Re: user process

Dennis Handly — Fri, 18 Jan 2008 08:45:26 GMT

>I would like to confirm you whether the logic is:
>it first read all pid in pid_file (kill -0),

It reads them all in the shell but it does them one by one.

>it try to kill it by "kill", if successful to kill, then do nothing, if unsuccessful to kill, then try kill -INT, if still not success, then try kill -QUIT, if still not success, then mailx, is the logic correct?

Yes, if you remove those debugging "echo"s and one "false".