为什么SSH远程命令会在手动运行时获得更少的环境变量？

我有一个运行正常的命令,如果我ssh到一台机器并运行它,但当我尝试使用远程ssh命令运行它时失败,如:

ssh user@IP 

使用两种方法比较"env"的输出在不同环境中重新进行.当我手动登录到机器并运行env时,我运行时会获得更多的环境变量:

ssh user@IP "env"

知道为什么吗？

1> Vinko Vrsalo..：

---

有不同类型的贝壳.SSH命令执行shell是非交互式shell,而普通shell是登录shell或交互式shell.描述如下,来自man bash:

       A  login  shell  is  one whose first character of argument
       zero is a -, or one started with the --login option.

       An interactive shell is  one  started  without  non-option
       arguments  and  without the -c option whose standard input
       and error are both connected to terminals  (as  determined
       by  isatty(3)), or one started with the -i option.  PS1 is
       set and $- includes i if bash is interactive,  allowing  a
       shell script or a startup file to test this state.

       The  following  paragraphs  describe how bash executes its
       startup files.  If any of the files exist  but  cannot  be
       read,  bash reports an error.  Tildes are expanded in file
       names as described below  under  Tilde  Expansion  in  the
       EXPANSION section.

       When  bash is invoked as an interactive login shell, or as
       a non-interactive shell with the --login option, it  first
       reads and executes commands from the file /etc/profile, if
       that file exists.  After reading that file, it  looks  for
       ~/.bash_profile,  ~/.bash_login,  and  ~/.profile, in that
       order, and reads and executes commands from the first  one
       that  exists  and is readable.  The --noprofile option may
       be used when the shell is started to inhibit  this  behav­
       ior.

       When a login shell exits, bash reads and executes commands
       from the file ~/.bash_logout, if it exists.

       When an interactive shell that is not  a  login  shell  is
       started,  bash reads and executes commands from ~/.bashrc,
       if that file exists.  This may be inhibited by  using  the
       --norc  option.   The --rcfile file option will force bash
       to  read  and  execute  commands  from  file  instead   of
       ~/.bashrc.

       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 command
       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 user @ host"bash --login -c"命令arg1 ...'"`将使远程shell设置登录环境.你引用的部分确实提到了`--login`,但很容易忽略这一点.

---

很好的答案,这正是问题所在,所需的环境变量存在于/ etc/bashrc中,而这些变量并非以非交互模式提供.将它们移动到/ etc/profile解决了这个问题.非常感谢你!

2> Ian Vaughan..：

---

在运行命令之前如何获取配置文件？

ssh user@host "source /etc/profile; /path/script.sh"

您可能会发现最好的改变,要~/.bash_profile,~/.bashrc或什么的.

(如此(linuxquestions.org))

---

必须始终键入额外的代码只是为了获取环境是荒谬的!

---

一个很少重复输入这些东西,通常它会在一个脚本中,因此,无论有多少"额外代码",只要它有效:tm:

3> dpedro..：

---

运行远程ssh命令时不加载Shell环境.您可以编辑ssh环境文件:

vi ~/.ssh/environment

其格式为:

VAR1=VALUE1
VAR2=VALUE2

另外,检查PermitUserEnvironment = yes选项的sshd配置.

4> tomaszbak..：

---

我有类似的问题,但最后我发现〜/ .bashrc就是我所需要的.

但是,在Ubuntu中,我不得不评论停止处理〜/ .bashrc的行:

#If not running interactively, don't do anything
[ -z "$PS1" ] && return

---

或者,您可以将所有"非交互式"代码放在该行之上.