[SOLVED] I try kill <pid> but program still appearws if I use ps
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You have to send kill signal to terminate the process. You can do this using following command:
kill -9 <pid of that process>
-9 is the kill signal.
Thanks, I have investigated further and if I do not specify the signal to send then SIGTERM is sent. I presume the application had a handler for SIGTERM and just carried on running. No program can handle SIGKILL (-9) (as far as I am aware) so that did the trick.
When processes are killed with SIGKILL they have no opportunity to clean up before they stop so data may be lost and files may be left in an uncoordinated state. For these reasons, if the application can be stopped by any other signal, that signal should be used. SIGKILL is a last resort (unless you want the process to have no opportunity to save its data ).