Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!think!nike!lll-crg!lll-lcc!well!mitsu
From: mitsu@well.UUCP (Mitsuharu Hadeishi)
Newsgroups: net.micro.amiga
Subject: Re: 1.2 RUN command STILL ISN'T FIXED!
Message-ID: <1330@well.UUCP>
Date: Tue, 24-Jun-86 19:46:01 EDT
Article-I.D.: well.1330
Posted: Tue Jun 24 19:46:01 1986
Date-Received: Fri, 27-Jun-86 04:05:48 EDT
References: <9300011@ti-csl>
Reply-To: mitsu@well.UUCP (Mitsuharu Hadeishi)
Organization: Whole Earth Lectronic Link, Sausalito CA
Lines: 14
Keywords: run, priority, unix, keywords
Summary: RUN shouldn't set priority to -5!!!

----)

	In re: RUN setting priority to -5
	Run should NOT set the priority to -5 automatically.  This
should DEFINITELY be an OPTION.  The reason for this is the scheduler
in the Amiga multitasking kernal does NOT operate in the same way as
Unix.  On Unix, a task with a lower priority gets less CPU time.  On
the Amiga, a task with a lower priority gets NO cpu time AT ALL until
ALL tasks with a higher priority are in a Wait() state.  This could
easily lead to a lower priority process getting locked out if a
computationally intensive task is running at a higher priority.  All
sorts of bad things can happen, too, if your program creates a task
at a higher priority than itself and . . . you get the picture.
				-Mitsu (mitsu@well.UUCP)