01-09-2003
set +o bgnice
is the command to tell the shell to not renice background jobs. Just run that command before you launch your background jobs.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi! Experts,
Is there anyway to incerase the priority of a process which is already started and running??.. I think nice can used for increase priority when we start the process..
But donno how to do when its already running..
Any help would be apreciated..
Jyoti (2 Replies)
Discussion started by: jyotipg
2 Replies
2. 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
3. Solaris
hello,
I have a process lauched by non-root user.
how to lauch this process with a very high priority?
I know this has to do with nice command but how to allow a user to lauch his process with a very high priority and without ROOT intervention?
PS: this process is always lauched from a... (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
4. UNIX for Dummies Questions & Answers
how to decrease priority of a particular process in time of process creation...
and also how to decrease priority of a particular process after process creation..
can any one please help me out... (2 Replies)
Discussion started by: Ramkum
2 Replies
5. AIX
hi how to change the priority of a process for eg.if a,b,c these there process are running and if i have to give the b process as high priority and high severe level what should i do (3 Replies)
Discussion started by: senmak
3 Replies
6. AIX
Hi all!
Some dumb administrator run the weekly backup "by hand" on our AIX 5.3 server, which we use to deploy Websphere applications, during work hours. Using the server while the backup is taking place is almost imposible. Both the disks are working at 100% and it's almost unusable. Asking the... (2 Replies)
Discussion started by: shandrio
2 Replies
7. AIX
One issue I could see on AIX 5.3: At one of my customer they have got the ThreadLimit of 2500 set on web server in httpd.conf file.
Currently 2000 users have logged in each attaing a single instance of httpd.
While in ps -ef for httpd process it is showing thread count (thcount) almost 3000.... (3 Replies)
Discussion started by: aarora_98
3 Replies
8. UNIX for Dummies Questions & Answers
Dear Masters,
I need to eliminate lines from file input 2 when the date in column 1 more than date in column 1 in file input 1
input 1
20141101|USA|CANSEL|496420000
20141101|USA|CANUT|1069740000
20141101|USA|CANTENG|625920000
20141102|USA|CANUT|413180000
20141103|USA|CANSEL|1364245000... (5 Replies)
Discussion started by: radius
5 Replies
LEARN ABOUT PLAN9
queuedefs
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)