Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!apple!motcsd!hpda!hpcuhb!hpindda!ferneau
From: ferneau@hpindda.HP.COM (Mark Ferneau)
Newsgroups: comp.sys.hp
Subject: Re: A Free Terminal
Message-ID: <4310092@hpindda.HP.COM>
Date: 1 Feb 90 00:12:23 GMT
References: <7748@lindy.Stanford.EDU>
Organization: Cupertino's Best Roadkill Establishment
Lines: 30

> I have a primitive question about launching background jobs (or
> processes) without tying up an end-user terminal. 

Sounds simple enough--and remember no question is "primitive".
If you look at the man page(s) for the shell
you are using (sh, csh, or ksh), they each describe how to execute
commands in the background.  See "Commands" under sh(1), "Jobs" under csh(1)
or ksh(1).

Basically for a command named "boffo", you just type (at the beautiful unix
shell prompt):

	 boffo &
	       ^ notice that nifty symbol.  This tells the shell to execute
"boffo" in the background.  Of course if boffo wants to use stdin or stdout
it won't get too far--but that brings us to the next question...

> As a bonus question, I would even be more grateful if you could tell
> me how I could redirect the output of the rje program to a file
> instead of the default output which is the terminal screen.

O.k.  if I answer this one, what prize do I get?? :-)
Once again, if you look at the aforementioned man pages under the
section entitled "Input/Output" it will describe all of the options for
what you describe.  To continue on the above example...  To save the
output from "boffo" to a file named "zowee" AND run it in the background,
the following should suffice:
	boffo > zowee &

How's that?