07-14-2009
The nice command breaks ties between processes that would otherwise be treated identically by the kernel. And it only effects processes while they are cpu bound. If a process is waiting for I/O to complete, it must wait regardless of how little niceness it has.
But I am a little tempted to rewrite readline to check the nice value. If the process has negative niceness, it would wait 5 seconds then issue a hurry-up message.... "Hey! Let's speed it up! I don't have all day!"
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can someone tell me .. how to find a user & process who has executed nice (scheduled priority) to one of his process. .Tks.. (5 Replies)
Discussion started by: sivan
5 Replies
2. UNIX for Advanced & Expert Users
Under, Solaris 10 I have the following problem:
A script executed at command line runs with nice level 0, as expected.
Same script started under (user) crontab runs with nice level 2.
I would prefer it run at 0. Is this possible? If so, how?
Thanks. (0 Replies)
Discussion started by: henrydark
0 Replies
3. UNIX for Dummies Questions & Answers
Can someone tell me this. thanks (1 Reply)
Discussion started by: xoxouu
1 Replies
4. Programming
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
Discussion started by: tejbuch
2 Replies
5. UNIX for Dummies Questions & Answers
hello everybody:
I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it... (1 Reply)
Discussion started by: aladdin
1 Replies
6. Shell Programming and Scripting
Hello,
I am just starting with shell scripting, as everyone will soon see from my question. What I'm trying to do is call the Nice command to set the script process priority from /bin/ksh. The difference is I'm running it not directly through the shell, but through Bigfix (very similar to... (3 Replies)
Discussion started by: solly119
3 Replies
7. Shell Programming and Scripting
Dear Friends,
I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Discussion started by: learnbash
6 Replies
8. BSD
Hello Folks,
Recently our FreeBSD 7.1 i386 system became very sluggish.
Nothing much is happening over there & whatever is running takes eternity to complete.
All the troubleshooting hinted towards a very high nice percentage.
Can that be the culprit?
Pasting snippets of top command,... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies
9. Shell Programming and Scripting
with using wall command, how can i have a carriage return in my broadcast message. i try to broadcast from a file, i were to use "cat myfile | wall" for broadcasting. but when the message broadcast somehow the format run away.
this the text in my file:
line 1
line 2
line 3
when broadcast
... (3 Replies)
Discussion started by: lsy
3 Replies
RENICE(1) BSD General Commands Manual RENICE(1)
NAME
renice -- alter priority of running processes
SYNOPSIS
renice [-n] priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]
renice -h | -v
DESCRIPTION
Renice alters the scheduling priority of one or more running processes. The following who parameters are interpreted as process ID's,
process group ID's, or user names. Renice'ing a process group causes all processes in the process group to have their scheduling priority
altered. Renice'ing a user causes all processes owned by the user to have their scheduling priority altered. By default, the processes to
be affected are specified by their process ID's.
Options supported by renice:
-n, --priority
The scheduling priority of the process, process group, or user.
-g, --pgrp
Force who parameters to be interpreted as process group ID's.
-u, --user
Force the who parameters to be interpreted as user names.
-p, --pid
Resets the who interpretation to be (the default) process ID's.
-v, --version
Print version.
-h, --help
Print help.
For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root.
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
(for security reasons) within the range 0 to PRIO_MAX (20), unless a nice resource limit is set (Linux 2.6.12 and higher). The super-user
may alter the priority of any process and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20
(the affected processes will run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to
make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
The Linux kernel (at least version 2.0.0) and linux libc (at least version 5.2.18) does not agree entirely on what the specifics of the sys-
temcall interface to set nice values is. Thus causes renice to report bogus previous nice values.
HISTORY
The renice command appeared in 4.0BSD.
AVAILABILITY
The renice command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
4th Berkeley Distribution June 9, 1993 4th Berkeley Distribution