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.
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.
Any ideas? Rebooting seems to work, but there must be a better way. I've tried sending all sorts of other signals to them, too, but signal 9 is supposed to be the no-questions asked, die-right-now signal, right?
Thanks, I will have to try that next time it happens... I did try viewing the processes using gtop, which does a kind of hierarchical categorization of them also, but it didn't look like there were any parent processes really.
Well, I now know how to view processes hierarchically... however, killing wine still does not seem to work. The process listing does not seem to show any particular wine process as the parent of another.
One thing I should note - there is usually a 'wineserver' process running, which can be killed. I don't know whether this affects anything, though. Obviously wineserver is not the parent of the wine processes, though.
What baffles me is why killall tells me that it has killed these processes when it clearly has not Why would my Linux lie to me? I feel so betrayed...
Any other suggestions? I refuse to believe that there is no way to do it... This happens pretty often, and I'd hate to have to restart every time wine poops out.
Okay, it appears the problem is not limited to Wine... at the moment, there are some Mozilla processes running that refuse to die. kill, killall, kill -9, killing by name or process number; none of them work, even when run as root. No errors, no nothing. (With verbose mode, killall even tells me it has killed them, same as above).
What is up with this? Has kill suddenly acquired a conscience? Does it feel bad about killing? Should I reinstall kill? Has this happened to anyone else? It is driving me slightly nuts!
I've noticed a trend... The four processes I have right now that won't die are either in uninterruptible sleep mode (D), or zombie (the child mozilla-bin process). From what I've seen, zombies are already dead, and are just waiting on their parent to acknowledge it - so that explains one of them.
And if the sleep is uninterruptible... how can it be interrupted?
How do sysadmins handle stuff like this, if they are not in a position to reboot?