Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Correct me if I'm wrong but won't the command: kill -9 XXXXX, kill the process no matter what? I have this process that has crashed and I can't get it to go away. I typed kill -9 23254, both in my user account and with su and it won't go away? I have had this problem before. What do I need to do to kill it and any other stubborn processes in the future that act the same way?
I have encountered similar problem. With kill -9 it doesn't work. And the parent process of the process I want to kill is 1. In this case, it is not allowed to kill 1. How to kill the hanging process? For me it is not possible to restart the system because it is shared by many people.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
If the process isn't a zombie so isn't reaped by init, there is a good chance it is hanging in the kernel in "uninterruptable sleep".
Depending on the driver used, you may fix that by reviving a disconnected peripheral (or a remote server if NFS is the culprit).
If the issue is a buggy device driver, I believe you have no alternative but to reboot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.