title: bash seems to ignore BASH_ENV when accessed through a symlink
body: <p>I'm working in a UNIX environment where <code>/bin</code> has been set up like this:</p>
  
  <pre><code>-rwxr-xr-x  1 root root 617144 Nov 19  2009 bash
  lrwxrwxrwx  1 root root      4 Nov 23  2010 sh -&gt; bash
  </code></pre>
  
  <p>In my environment I have set <code>$BASH_ENV</code> to point to my local .bashrc:</p>
  
  <pre><code>env | grep BASH
  BASH_ENV=/home/users/atomicpirate/.bashrc
  </code></pre>
  
  <p>In addition, .bashrc has as its first line <code>echo BASHRC READ</code>.</p>
  
  <p>I would expect /bin/sh and /bin/bash to behave exactly the same with this setup...but they don't:</p>
  
  <pre><code>/bin/bash -c 'echo $BASH_ENV'
  BASHRC READ
  /home/users/atomicpirate/.bashrc
  
  /bin/sh -c 'echo $BASH_ENV'
  /home/users/atomicpirate/.bashrc
  </code></pre>
  
  <p>In the second case, .bashrc is NOT read.  Any idea why this would be the case?  It seems like the symlink is breaking the expected behavior of $BASH_ENV.</p>