Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uwvax!tank!shamash!com50!jhereg!mark
From: mark@jhereg.Jhereg.MN.ORG (Mark H. Colburn)
Newsgroups: alt.sources
Subject: Re: renice
Message-ID: <910@jhereg.Jhereg.MN.ORG>
Date: 18 May 89 14:09:06 GMT
References: <62@utower.UUCP>
Reply-To: mark@jhereg.MN.ORG (Mark H. Colburn)
Organization: Minnetech Consulting, Inc., St. Paul, MN
Lines: 23

In article <62@utower.UUCP> fischer@utower.UUCP (Axel Fischer) writes:
>It's resets the priority of a process to a lower priority if the process
>runs longer than n minutes. n is configurable in the Makefile.
>So the machine is not to busy with the single process.
>(Maybe 2,3,4 ... minutes or whatever)

I think that you will find that you are just duplicating work.

The kernel already does this.  It does not adjust the visible nice value,
but there is a kernel internal interpretation of "priority" which is
adjusted by the kernel.  The nice value is used to help compute the
priority, as is run time.  Processes which run for a very long time have
their priority adjusted downward.  In order to keep processes from being
locked out on the swap device, processes which have not been in run-state
for a while will have their priorities adjusted upwards so that they can
get to run every once in a while.

If you are interested, a good book to read about this stuff is "The design
of the Unix Operating System" by Maurice Bach.

-- 
Mark H. Colburn                          mark@jhereg.mn.org
Minnetech Consulting, Inc.