Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
I've heard the kernel can kill a process that eats-up too much CPU time, and that it's configurable, however I don't see anything in sysctl that sounds similar. Anyone know if this feature exists? That is, I can tell the kernel "anything using more than 5 minutes CPU time, kill it"?
You could write a script to do that but it would be rather dangerous. Some things accumulate time throughout their lifecycle (monitoring tools are notorious for this) and killing them just because they had a lot of CPU time would hardly be reasonable.
You need to understand what is running on your system and determine impact of stopping it (and restarting if necessary). If you have commands that have a lot of CPU time it would be better to understand WHY they do (or accept that they do) than to kill them willy-nilly.
I understand the repercussions of killing processes using various criteria. I was wondering if the kernel was capable of doing this via either a compile-time parameter or at runtime (e.g., via sysctl), similar to various 3rd party tools like NetIQ. Thanks.