03-06-2013
Yes, it's a bit short sighted that UNIX ts mode login goes to the highest allowed priority, rather than somewhere in the middle, like 30. Then, users could tweak their background or other-terminal processes up or down using nice and renice. It's all relative, after all. I guess the real trick is to get out of time sharing into real time mode, like Windows' Realtime!
They even put a 'bgnice' option in ksh at some point, so you could make all background processes nicer by default.
9 More Discussions You Might Find Interesting
1. Linux
Hello!
How do make the limits.conf parameters work for a normal user. Ive changed
both the hard and soft parameter for the specific user. It used to be 4096 and i changed it to 16384. But when i use the ulimit -n, all i got is permissen denied.
Witch i can understand. But my question is? how... (1 Reply)
Discussion started by: dozy
1 Replies
2. UNIX for Dummies Questions & Answers
I have line in this file that says:
username - maxlogins 1
and user can login 2 times instad of one.
does enybody know why? and how can I fix that? (2 Replies)
Discussion started by: shooroop
2 Replies
3. HP-UX
Hi folks,
Hope you can help me. I have a process that is currently running at nice 20 and need it to run faster (-10?). How do I change the process using nice? I have the process number and thought it would be along the lines of;
nice -10 process_id
but it doesn't seem to like that. (1 Reply)
Discussion started by: gshuttleworth
1 Replies
4. UNIX for Advanced & Expert Users
HI,
To restrict the number of files and number of processes used the user we use the following configuration in the file /etc/security/limits.conf.
oracle soft nofile 65572
oracle hard nofile 65572
oracle soft noproc 16384
oracle soft noproc 16384
My question is what do the 'soft' and... (1 Reply)
Discussion started by: praveen_b744
1 Replies
5. Solaris
Hi,
How can we set per user core file size, etc in solaris, i.e. I want solaris counterpart/equivalent of linux /etc/security/limits.conf.
TIA (0 Replies)
Discussion started by: slash_blog
0 Replies
6. Red Hat
Hello all,
I'm running Oracle 10.2 on RHEL5. Current value of ulimit -n is set to a low value of 1024. I need to increase it to 65536 using the following procedure.
cat >> /etc/security/limits.conf <<EOF
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard... (3 Replies)
Discussion started by: luft
3 Replies
7. Red Hat
i want to set limits in /etc/security/limits.conf.My os is rhel 5.2.
It was giving continuous messages in in /var/log/secure like :
continuously.
I have changed values of priority and nice to "0" from unlimited and messages are not comming. But i want to know what is the ideal/maximum... (3 Replies)
Discussion started by: pankajd
3 Replies
8. 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
9. UNIX for Dummies Questions & Answers
OS version : RHEL 6.5
Below is an excerpt from /etc/security/limits.conf file for OS User named appusr in our server
appusr soft nproc 2047
appusr hard nproc 16384
What will happen if appusr has already spawned 2047 processes and wants to spawn 2048th process ?
I just want to know... (3 Replies)
Discussion started by: kraljic
3 Replies
LEARN ABOUT NETBSD
renice
RENICE(8) BSD System Manager's Manual RENICE(8)
NAME
renice -- alter priority of running processes
SYNOPSIS
renice priority [[-p] pid ...] [-g pgrp ...] [-u user ...]
renice -n increment [[-p] pid ...] [-g pgrp ...] [-u user ...]
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:
-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.
-p Resets 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: 0, the ``base'' scheduling priority; 20, the affected processes will run only when nothing at the base priority wants
to; anything negative, the processes will receive a scheduling preference.
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
nice(1), getpriority(2), setpriority(2)
HISTORY
The renice command appeared in 4.0BSD.
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.
BSD
June 9, 1993 BSD