From 22c445f3eb3c77dbc35def9994d3c1e793b48882 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 18 Apr 2015 16:07:02 -0400 Subject: [PATCH] response --- ...ent_1_1fafdc4ed4a0f601918361dca688aa6c._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Cant_see_git-annex-shell_via_SSH_in_OSX/comment_1_1fafdc4ed4a0f601918361dca688aa6c._comment diff --git a/doc/forum/Cant_see_git-annex-shell_via_SSH_in_OSX/comment_1_1fafdc4ed4a0f601918361dca688aa6c._comment b/doc/forum/Cant_see_git-annex-shell_via_SSH_in_OSX/comment_1_1fafdc4ed4a0f601918361dca688aa6c._comment new file mode 100644 index 0000000000..edbf2edfc4 --- /dev/null +++ b/doc/forum/Cant_see_git-annex-shell_via_SSH_in_OSX/comment_1_1fafdc4ed4a0f601918361dca688aa6c._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-04-18T20:05:42Z" + content=""" +This is a common gotcha; bash sources something like .bashrc +or whatever that puts /usr/local/bin/ in your path when it's a login shell. +However, when git-annex is sshing in, there is no login shell, +and bash does not source any dotfiles, and so git-annex-shell in not in +PATH. + +The solution is probably to move or symlink it to some other directory +that is in PATH always. +"""]]