07-14-2009
nice changes base priority. Unless you are superuser, it only decreases your priority relative to other processes on the system.
Note: Priority numbers are backwards, higher priority number == lower priority
The OS scheduler can change (up or down) priority. However if your base priority is lower than everyone else logged on, a temporary boost will still have you below the "crowd". ALL non-realtime processes can have process priority changed for a lot of reasons. This is normal.
No way is nice a "myth".
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
LEARN ABOUT FREEBSD
rtprio
RTPRIO(1) BSD General Commands Manual RTPRIO(1)
NAME
rtprio, idprio -- execute, examine or modify a utility's or process's realtime or idletime scheduling priority
SYNOPSIS
[id|rt]prio
[id|rt]prio [-]pid
[id|rt]prio priority command [args]
[id|rt]prio priority -pid
[id|rt]prio -t command [args]
[id|rt]prio -t -pid
DESCRIPTION
The rtprio utility is used for controlling realtime process scheduling.
The idprio utility is used for controlling idletime process scheduling, and can be called with the same options as rtprio.
A process with a realtime priority is not subject to priority degradation, and will only be preempted by another process of equal or higher
realtime priority.
A process with an idle priority will run only when no other process is runnable and then only if its idle priority is equal or greater than
all other runnable idle priority processes.
Both rtprio or idprio when called without arguments will return the realtime priority of the current process.
If rtprio is called with 1 argument, it will return the realtime priority of the process with the specified pid.
If priority is specified, the process or program is run at that realtime priority. If -t is specified, the process or program is run as a
normal (non-realtime) process.
If -pid is specified, the process with the process identifier pid will be modified, else if command is specified, that program is run with
its arguments.
Priority is an integer between 0 and RTP_PRIO_MAX (usually 31). 0 is the highest priority
Pid of 0 means "the current process".
Only root is allowed to set realtime or idle priority for a process. A user may modify the idle priority of their own processes if the
sysctl(8) variable security.bsd.unprivileged_idprio is set to non-zero. Note that this increases the chance that a deadlock can occur if a
process locks a required resource and then does not get to run.
EXIT STATUS
If rtprio execute a command, the exit value is that of the command executed. In all other cases, rtprio exits 0 on success, and 1 for all
other errors.
EXAMPLES
To see which realtime priority the current process is at:
rtprio
To see which realtime priority of process 1423:
rtprio 1423
To run cron(8) at the lowest realtime priority:
rtprio 31 cron
To change the realtime priority of process 1423 to 16:
rtprio 16 -1423
To run tcpdump(1) without realtime priority:
rtprio -t tcpdump
To change the realtime priority of process 1423 to RTP_PRIO_NORMAL (non-realtime/normal priority):
rtprio -t -1423
To make depend while not disturbing other machine usage:
idprio 31 make depend
SEE ALSO
nice(1), ps(1), rtprio(2), setpriority(2), nice(3), renice(8)
HISTORY
The rtprio utility appeared in FreeBSD 2.0, but is similar to the HP-UX version.
AUTHORS
Henrik Vestergaard Draboel <hvd@terry.ping.dk> is the original author. This implementation in FreeBSD was substantially rewritten by David
Greenman.
CAVEATS
You can lock yourself out of the system by placing a cpu-heavy process in a realtime priority.
BUGS
There is no way to set/view the realtime priority of process 0 (swapper) (see ps(1)).
There is in FreeBSD no way to ensure that a process page is present in memory therefore the process may be stopped for pagein (see
mprotect(2), madvise(2)).
Under FreeBSD system calls are currently never preempted, therefore non-realtime processes can starve realtime processes, or idletime pro-
cesses can starve normal priority processes.
BSD
September 29, 2012 BSD