[Borgbackup] borg can't find executable on remote

[Steve Schow]

I notice the error message that comes back is a bash error…so can someone confirm that borg is actually calling bash to indirectly call borg through the bash shell, as opposed to call borg directly?


 
On May 11, 2016, at 8:24 PM, Dan Christensen <jdc at uwo.ca> wrote:

> The shell on the remote end should run the .bashrc init file,
> and environment variables can be set there.  There are other ways
> too, but this is getting off topic for the list.
> 
> Dan
> 
> On May 11, 2016, Steve Schow <steve at bstage.com> wrote:
> 
>> That makes sense.  Do you know if there is a way to provide env settings to ssh calls?
>> 
>> Sent from my iPhone
>> 
>>> On May 11, 2016, at 5:42 PM, Dan Christensen <jdc at uwo.ca> wrote:
>>> 
>>>> On May 11, 2016, Steve Schow <steve at bstage.com> wrote:
>>>> 
>>>> is there any reason by borg’s method of calling SSH would not get the user’s env?
>>> 
>>> "Login" shells run extra init scripts, such as .profile.  Compare what
>>> happens if you login to the remote machine, and then type "echo $PATH":
>>> 
>>> ssh user at remote
>>> echo $PATH  [in the remote shell]
>>> 
>>> vs. what happens if you run
>>> 
>>> ssh user at remote 'echo $PATH'
>>> 
>>> (Note the single quotes, so the $PATH variable gets expanded on the
>>> remote end.)
>>> 
>>> The latter doesn't create a login shell.
>>> 
>>> As was suggested, the --remote-path option will solve this for you.
>>> Or, you can set your path in your .bashrc file, which is run in both
>>> cases.
>>> 
>>> Dan