Shell Programming and Scripting

i have one script which uses “kill -9” command. That prevents from getting the process core dumps. Apparently once tomcat lands in a confused state, we seem to have no other option, other than Kill -9.

is there any other way to get rid of this.

Script:

Code:

sleep 2
PID=`ps -ef | grep "^tomcat " | grep -v grep | grep Bootstrap | awk '{print $2}'`
if [ "$PID" != "" ] ; then
  echo "Killing process."
  kill $PID
  sleep 5
  PID=`ps -ef | grep "^tomcat " | grep -v grep | grep Bootstrap | awk '{print $2}'`
  if [ "$PID" != "" ] ; then
    echo "Force killing process"
    kill -9 $PID
  fi

Any idea will be highly appriciated

Moderator's Comments:

Neo: Changed Thread Title for User. Please follow forum rules and use a descriptive subject text useful to others.

Off the top of my head, I'd say that tomcat is ignoring TERM (15) signals (the default when you only provide a PID to the kill command). This is why 'kill $PID' seems not to work. It is likely ignoring HUP (1) and QUIT (3) signals too.

I'm not really sure what this is that you are wanting to get rid of. The running process, the script, the need for kill -9?

I'll go on the assumption that you are wanting to cause a core dump which is not produced when using -9 (SIGKILL). Try using 'kill -6' (abort) -- I'd hope that the tomcat developers left this signal set to it's default value (terminate programme and generate a core dump).

Thanks for your reply.

Yes u r correct, i want the core dump which is not produced using kill -9.

can i use kill -3 ?

Thank you very much for giving me an way

You can try kill -3, however that signal is often disabled or caught and processed by daemons such as tomcat. If it works, great, but I wouldn't be surprised to find that it has the same effect as kill -15. I don't run tomcat, so I can't play round with it to tell you more than this.