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.
I have been able to use 'nice' and 'renice' to set priorities of processes but I run into a few weird problems with 'renice'. When I start an application without 'nice' I get the default priority of 0 and when I manually set the priority using 'nice' it works fine. BUT when a process is already running (with either the default priority or the newly set one) I can't only renice to the current priority and lower. I get a permission denied if I try to go higher. I think this example will make it clear:
I did a quick play at the command line myself, and it would appear that regular users cannot 'unnice' their own processes. I knew that reg users couldn't negative nice anything, but it seems odd that they cannot bring the priority back to the default of '0'.
Try as root and you can set them lower (higher?) again...
Well I can use root to do anything on my own systems, but if I had root access on the system in question I wouldn't worry about nice'ing anything as I wouldn't be nice. But it isn't my system so I don't have root... I too just thought it was odd that I coulded renice my processes (as long as I stayed over 0). There must be a reson for that though...
Altering Process Priority
Users other than the privileged user may only alter the
priority of processes they own, and can only monotonically
increase their "nice value" within the range 0 to 19. This
prevents overriding administrative fiats.
So once you've lowered the priority of a process, your screwed. Of course I'm assuming that nobody has re-written renice for Linux and we're all just using the UNIX version
Good call. I read that paragraph paying close attention to "Users other than the privileged user may only alter the priority of processes they own" and selectively ignoring "and can only monotonically increase their "nice value""