Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/12/84; site azure.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!mhuxn!houxm!ihnp4!zehntel!hplabs!tektronix!teklds!azure!scottha
From: scottha@azure.UUCP (Scott Hankerson)
Newsgroups: net.unix-wizards
Subject: Re: automatic re-nicing of processes
Message-ID: <3@azure.UUCP>
Date: Wed, 5-Dec-84 04:46:52 EST
Article-I.D.: azure.3
Posted: Wed Dec  5 04:46:52 1984
Date-Received: Fri, 7-Dec-84 02:12:46 EST
References: <5937@brl-tgr.ARPA>
Reply-To: scottha@azure.UUCP (Scott Hankerson)
Organization: Tektronix, Beaverton OR
Lines: 18
Summary: 

In article <5937@brl-tgr.ARPA> Mark Crispin  writes:
>
>     I'm a bit bewildered as to why this code should be necessary.
>Computational processes, especially those with small memory usage,
>should have little or no impact on the system except to other
>computational processes.  An operating system typically always has
>such a process running; it's called the null job and often does
>such useful tasks as counting to infinity.
>
>     Isn't Unix's scheduler smart enough to do this?  I thought it
>had been rewritten since the toy scheduler which existed in PDP-11
>days?
>-------

You don't really want a null process to be scheduled at the same
priority as your own process do you?  Generally such processes are
to be scheduled at very low priorities so that they are only
continued when nothing else is running.