Sponsored Content
Full Discussion: recursive nice value
Top Forums UNIX for Advanced & Expert Users recursive nice value Post 302127541 by jgt on Wednesday 18th of July 2007 12:29:29 PM
Old 07-18-2007
From the man page for nice:

By default, background jobs run by the Bourne and Korn shells are
assigned a nice value four greater than that of the parent shell.
The ksh(C) option +o bgnice disables this behavior, causing
background processes to run with the same nice value as the
parent shell.

So this begs the question, if you are only using two different nice levels (20 , the default and 24, for background) is the distribution of system resources different than if you had used 20 and 39?
 

6 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Very Nice

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. Programming

nice command and nice() system call

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

3. UNIX for Dummies Questions & Answers

The nice command

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

4. HP-UX

top and nice

Hi, I have two identical 12 CPU HPUX machines, and I run the same processes on each that load the boxes fully. top on one reports activity under the NICE (19%) and SYS (18%) columns, while top on the other reports 0% NICE and 16% SYS. What would cause NICE to be zero on one machine and not... (5 Replies)
Discussion started by: CBorgia
5 Replies

5. AIX

nice and renice

hello , We would like to increase the priority of the oracle process . Process(240001 ) should get the priority like the process(240103 ). Am not sure what value i should mention in the renice command(aix 6.1). Please assist me. 240001 A oracle 26804312 1 0 60 20... (2 Replies)
Discussion started by: gowthamakanthan
2 Replies

6. Shell Programming and Scripting

How to use nice command?

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
queuedefs(4)                                                       File Formats                                                       queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 07:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy