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.
Can you show us the results of ps aux | grep <pid>. Also, can you check that, having killed the parent, that the child process has been adopted by init (its parent process ID should now be 1). You can quickly do this with "ps -o ppid pid".
If the process is in state "D" as opposed to "S", then it is in uninterruptable sleep, usually because of I/O, and it cannot be killed by any means until whatever operation put it in uninterruptable sleep completes. If it's in state "S", kill -9 should've taken care of it, so I'm a bit confused...
The result of ps aux | grep <pid> shows me the same entry for that pid even after killing the child & parent both & the parent id for that child process is 11. Also after killing the process, I had waited for 30 mins but still I see the same entry in ps.
Also the process is in sleeping state & not D state as I cannot show the print screen due to security reasons.