On Thu, Feb 17, 2011 at 11:04:12AM +0100, Stephan Beal wrote: > On Wed, Feb 16, 2011 at 6:25 PM, Richard Hipp <[email protected]> wrote: > > > My current approach is to run ssh to a shell on the remote side and then > > issue shell command over the wire that invoke Fossil multiple times to act > > as a server for the client-side protocol. It's all a bit dodgy. > > > > git uses this approach as well, as far as i can determine, and i have found > that this approach (which seems sane to me) breaks when hosters (like mine) > hard-code the PATH to /usr/bin:/bin for non-interactive shells. That of > course breaks when fossil/git/whatever is installed in ~/bin (as on my > setup). Because of fossil's built-in CGI support, it's still the only SCM > i've ever been able to get running on my hoster (where i cannot run custom > server processes). Non-interactive shells are usually non-login. And non-login shells run .bashrc, and not .bash_profile. Login-shells run .bash_profile, and not .bashrc.
I imagine you have the PATH addition to ~/bin in .bash_profile, and not in .bashrc, but in this case it is a problem of your HOME configuration, and not a problem of your provider. The MOTD should be shown only for login shells. And any program trying to run a remote command should use non-login shells. "ssh remotehost" will run a login interactive shell. "ssh -T remote" will run a login non-interactive shell. And "ssh remote sh" (regardless of -T) will run a non-login non-interactive shell. Please correct me if I am wrong; I just think that noone finds this information of any relevance in this thread. Regards, Lluís. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
