02-06-2007
Use nice when you invoke the command, else use renice if the process is already running.
The man pages for both commands clearly detail options and usage.
Cheers
ZB
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Just a quick message to say great work to Neo and any others who have helped with the upgrade - the layout, appearance and functionality of this forum ROCKS.
By far the best I have seen.
Excellent! (1 Reply)
Discussion started by: alwayslearningunix
1 Replies
2. 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
3. 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
4. UNIX for Dummies Questions & Answers
Can someone tell me this. thanks (1 Reply)
Discussion started by: xoxouu
1 Replies
5. 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
6. UNIX for Advanced & Expert Users
Hello,
Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Discussion started by: psimoes79
4 Replies
7. 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
8. 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
9. 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
10. 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
LEARN ABOUT OPENDARWIN
renice
RENICE(8) BSD System Manager's Manual RENICE(8)
NAME
renice -- alter priority of running processes
SYNOPSIS
renice [priority | [-n increment]] [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]
DESCRIPTION
The renice utility alters the scheduling priority of one or more running processes. The following who parameters are interpreted as process
ID's, process group ID's, user ID's or user names. The renice'ing of a process group causes all processes in the process group to have their
scheduling priority altered. The renice'ing of 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.
The following options are available:
-g Force who parameters to be interpreted as process group ID's.
-n Instead of changing the specified processes to the given priority, interpret the following argument as an increment to be applied to
the current priority of each process.
-u Force the who parameters to be interpreted as user names or user ID's.
-p Reset the who interpretation to be (the default) process ID's.
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''
within the range 0 to PRIO_MAX (20). (This prevents overriding administrative fiats.) 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
nice(1), rtprio(1), getpriority(2), setpriority(2)
STANDARDS
The renice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The renice utility appeared in 4.0BSD.
BUGS
Non super-users cannot increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in the
first place.
BSD
June 9, 1993 BSD