<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
</div></div>How about when they copy their .bashrc file - which might include<br>
PETSC_OPTIONS env variable? [or LD_LIBRARY_PATH to wrong version of<br>
libraries]<br>
<br></blockquote><div><br></div><div>This has never been a problem. Perhaps everyone know about .bashrc and must deal with it, but .petscrc falls of the radar and they/we forget about it ...<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is the current thought to remove PETSC_OPTIONS env variable aswell?<br></blockquote><div><br></div><div>Perhaps ~/.petscrc things can go into .bashrc somehow?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
How about PWD/.petscrc and PWD/petscrc? remove them aswell?<br></blockquote><div><br></div><div>These are the "normal" rc files that are really used to augment the command line. And in the case of FORTRAN codes, which don't add an arg parser of some sort, it is the command line.<br><br></div><div>Mark <br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Satish<br>
<br>
</font></span></blockquote></div><br></div></div>