dillon@CORY.BERKELEY.EDU (Matt Dillon) (04/30/86)
>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