Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site dg_rtp.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!mcnc!rti-sel!dg_rtp!throopw
From: throopw@dg_rtp.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Unix standard output buffer problem
Message-ID: <203@dg_rtp.UUCP>
Date: Thu, 6-Mar-86 18:46:32 EST
Article-I.D.: dg_rtp.203
Posted: Thu Mar  6 18:46:32 1986
Date-Received: Sat, 8-Mar-86 21:24:51 EST
References: <1421@brl-smoke.ARPA>
Lines: 22

> I have checked the exec source and it does not appear to mess
> with it [alter the whether-to-buffer flag] either.

Uh.... yeah.  I'm not sure what you think "exec" does, but on most
Unix(*)-like operating systems it does indeed "mess with" *all* the
globally persistant variables in the executable image it creates.  In
particular, it *creates* them all, giving them the values assigned them
at link-time.

To answer your question directly, there is *no* *way* to do what you
said you wanted to do.  Altering an address space before an exec had
*better* *not* have any effect on the address space seen after the exec,
or exec just isn't doing it's job.  The only way to alter the address
space gotten by execing an executable image is to patch the image on
disk (or link a new one).

> William Faulkner
--
* Unix is a trademark of ATT
-- 
Wayne Throop at Data General, RTP, NC
<the-known-world>!mcnc!rti-sel!dg_rtp!throopw