Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: More on the run command
Message-ID: <8604301550.AA06838@cory>
Date: Wed, 30-Apr-86 11:50:29 EDT
Article-I.D.: cory.8604301550.AA06838
Posted: Wed Apr 30 11:50:29 1986
Date-Received: Fri, 2-May-86 22:16:21 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 30


>A. Background jobs by default get no terminal input
>B. Unix has a scheduler that adjusts priorities.
>BOTH of these assumptions FAIL on the amiga.

	Yup.  They fail in a very bad way.  If you have one job at 0, and 
another at -5, and the one at 0 never sleep's or uses I/O, then the one at
-5 never gets run...

>I recently had to change my startup-script to 'run loadwb' just so that
>the 'run execute' command i have in there starts up competitive jobs.

	The program I posted,  'sr' (for search and replace), allows you to 
modify your 'run' command to run programs at standard priority.

>IF you can get newcli to take a command script THEN I will agree that
>run should set a lower priority.

	I don't agree.  RUN should run stuff at priority 0 (or actually, the
priority of the cli RUN was executed from), or you should be able to set the
priority.

>Unfortunatly, the original window refuses to go away if there is any
>'run command' task still active.
>			Michael Gersten

	Right... I noticed that too.  It would seem that the CLI cannot
exit until it's children vanish.

					-Matt