Xref: utzoo comp.windows.x:24121 comp.unix.questions:23595
Path: utzoo!attcan!uunet!convex!starman.Berkeley.EDU!bros
From: bros@convex.com
Newsgroups: comp.windows.x,comp.unix.questions
Subject: Re: Process priorities and X
Message-ID: <103717@convex.convex.com>
Date: 6 Jul 90 14:12:46 GMT
References: <1990Jul4.160042.562@smsc.sony.com> <9007031747.AA05025@stc06.CTD.ORNL.GOV> <1990Jul4.061431.12129@servalan.uucp>
Sender: news@convex.com
Reply-To: bros@1.com
Followup-To: comp.windows.x
Lines: 22

In article <1990Jul4.160042.562@smsc.sony.com>, dce@smsc.sony.com (David
Elliott) writes:

> In System V.2 and better versions of sh, the default is to automatically
> nice down (by 4) all processes started in the background.
> 
> In other words, it probably isn't twm starting the processes at a
> lower priority, but the shell.  If you have source for sh, you can
> recompile it to not nice down background jobs.  Another option is
> to write your own "background" command that runs, using the shell,
> the command[s] you need in the background (by forking and redirecting
> the process itself, instead of giving a & to the shell).
> as arguments 

The korn shell (ksh) has an option called "bgnice" which may be turned
off to prevent background jobs being niced.  You might check if your
shell has a similar option.


Andrew Bros				bros@convex.com
Product Engineering			or try:
Convex [Super]Computer Corp.		ab27@andrew.cmu.edu