Re: [PATCH 2/2] Remember and use GIT_EXEC_PATH on exec()'s

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jan 10, 2006, 20:15 UTC
Message-ID: <20060110201536.GA3155@steel.home>
In-Reply-To: <43C4075E.4070407@op5.se>

Andreas Ericsson, Tue, Jan 10, 2006 20:13:34 +0100:

Show 5 quoted lines

> >My shell's rc-file doesn't get invoked when using ssh as a transport;
> >that's part of the problem.
> 
> It does for me and everybody else. $HOME/.bashrc is read even for 
> non-interactive shells. ...

Not really:

$ man bash

       When bash is started non-interactively, to  run  a  shell  script,  for
       example, it looks for the variable BASH_ENV in the environment, expands
       its value if it appears there, and uses the expanded value as the  name
       of  a  file to read and execute.  Bash behaves as if the following com-
       mand were executed:
              if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi
       but the value of the PATH variable is not used to search for  the  file
       name.

$ ssh host2 strace -e open bash -c : open("/etc/ld.so.cache", O_RDONLY) = 3 open("/lib/libncurses.so.5", O_RDONLY) = 3 open("/lib/tls/libdl.so.2", O_RDONLY) = 3 open("/lib/tls/libc.so.6", O_RDONLY) = 3 open("/dev/tty", O_RDWR|O_NONBLOCK|O_LARGEFILE) = -1 ENXIO (No such device or address) open("/etc/mtab", O_RDONLY) = 3 open("/proc/meminfo", O_RDONLY) = 3 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 3