<br><br> <div class="gmail_quote">On Wed, Jan 13, 2010 at 5:41 PM, David Brown <span dir="ltr"><<a href="mailto:plt@davidb.org">plt@davidb.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="im">On Wed, Jan 13, 2010 at 05:33:10PM -0800, YC wrote:<br><br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I guess that will be the ways to go for now unless there are other<br>approaches.<br></blockquote><br></div> On Linux/Unix the 'env' program can be used as this executable to set<br>variables and run another program. If the cost of the extra exec<br>isn't a problem, this is probably the easiest way to get control over<br> the environment of a child process.<br></blockquote> <div> </div> <div> </div> <div>Thanks David for the pointer - I will look into env. </div> <div> </div> <div>Thanks,</div> <div>yc </div> <div> </div> <div> </div></div>