On Jul 3, 6:36 pm, Brian Dessent <[EMAIL PROTECTED]> wrote: > Add a temporary "echo" to your bashrc and see if you see that. If not, > figure out why the shell isn't running its startup files. But be sure > to remove the echo, because having a "clean" shell (i.e. free of stdout > spew) is important for commands that use ssh as transport, like git, > rsync and so on.
Hi Brian, thanks for the advice. It doesn't address the --upload-pack strangeness, but is useful in its own right as I try to navigate the SSH configuration issues. I tried what you said about the hello world echo by adding that to .bashrc. From tests related to that, it seems that even if I ssh interactively, only my .profile is getting sourced and not my .bashrc. Presumably non-interactive shells aren't even sourcing the .profile, hence the $PATH problems Git is having. I got suspicious when echo $0 says "-sh", yet I looked and saw that / bin/sh -> bash*. Maybe ssh is sneakily running sh from somewhere despite the bash symlink? Is there a better way of getting a straight answer on what shell is running, and whether it ran .bashrc? Thanks for your help, --- http://hostilefork.com
