Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 (Tek) 9/26/83; site hammer.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!tektronix!orca!hammer!dce
From: dce@hammer.UUCP (David Elliott)
Newsgroups: net.unix-wizards,net.bugs.4bsd
Subject: Re: automatic renice in 4.1 bsd?
Message-ID: <963@hammer.UUCP>
Date: Mon, 15-Oct-84 10:26:47 EDT
Article-I.D.: hammer.963
Posted: Mon Oct 15 10:26:47 1984
Date-Received: Sun, 21-Oct-84 12:54:59 EDT
References: <170@terak.UUCP> <190@rlgvax.UUCP>
Distribution: net
Organization: Tektronix, Wilsonville OR
Lines: 28
Xref: 10019 1142


> We have started to notice a problem with some
> people's login csh being reniced. Since we always
> have a few processes running, these people's terminal
> appears to be dead.
> 
> By reniceing the csh to 0, the terminal becomes alive
> again, and renice reports the old priority as 19.
> 
> Is there some thing in 4.1 bsd that renices people when
> the system load gets too high?

Another problem (besides the kernel renicing processes) is the csh
builtin command `nice'. If you look at the documentation, you will
see that `nice' with no arguments claims to set the nice of the current
shell to 4.

The code that attempts to do this does a nice(20), a nice(-10), and a
nice(4) (supposedly, this changes the nice to the maximum, back to 0,
and then to 4), but if you aren't the superuser, this sets the nice
to 19 and that's all. (Does anyone know why this would have worked
at some time?)

It is possible that someone inadvertently typed `nice' with no arguments,
or that you have a prankster going around typing `nice' on people's
terminals without them knowing.

			David