Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!ihnp4!chinet!ignatz
From: ignatz@chinet.UUCP (Dave Ihnat)
Newsgroups: comp.unix.wizards
Subject: Re: Redirecting shell output.
Message-ID: <1771@chinet.UUCP>
Date: Sat, 24-Oct-87 14:56:58 EST
Article-I.D.: chinet.1771
Posted: Sat Oct 24 14:56:58 1987
Date-Received: Mon, 26-Oct-87 04:34:03 EST
References: <289@minya.UUCP>
Reply-To: ignatz@chinet.UUCP (Dave Ihnat)
Organization: Analysts International Corp., Chicago
Lines: 24
Keywords: shell, redirection, files
Summary: That's not all you can do...

As many people have provided correct answers to the original redirection
query (i.e., to do something like "exec >fud 2>&1", I won't say it
here...

But nobody gave the fellow a little freebie that I don't see many
other people using; that is, you can open other files that way, too:

	exec 3>fred
	exec 4>charlie

Then, later, you can have specific output in the script go to these
files via, for instance,

	command >&4

Arcane, yes; but useful at times.  The biggest advantage is to open
one for input ("exec 4<foo"); subsequent "read INLINE <&4" will retain
their current positions in the file, unlike 'line'.  Note that you can
and *will* interact with any programs you're running in the script,
since you're opening file descriptors...
-- 
			Dave Ihnat
			ihnp4!homebru!ignatz || ihnp4!chinet!ignatz
			(w) (312) 882-4673