【问题标题】:Bash function doesn't work for remote ssh command execution although interactive shell function fine尽管交互式 shell 功能正常,但 Bash 功能不适用于远程 ssh 命令执行
【发布时间】:2019-03-11 06:49:52
【问题描述】:

我在.bash_aliases 文件中定义了一个函数,并将它包含在我的.bashrc 文件中。

我的.bash_aliases 文件:

function dmidecode() {
        if [[ $1 == -t && $2 == 1 ]]; then
                cat ~/some_file
        else
                command dmidecode "$@"
        fi
}

作用是:当有人执行命令:dmidecode -t 1时,bash从~/some_file中读取内容并返回。

我的.bashrc 文件:

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
        # We have color support; assume it's compliant with Ecma-48
        # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
        # a case would tend to support setf rather than setaf.)
        color_prompt=yes
    else
        color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi

当我通过在 bash shell 中键入命令以交互方式执行命令时,它会起作用。但是,当我尝试远程执行它时它不起作用。它说dmidecode command not found(我没有安装 dmidecode 工具,但我编写了一个函数将其指向某个地方。)。远程连接很好,因为我可以远程执行“ls”或“pwd”之类的命令。它只是不适用于我编写的函数。

我尝试将shopt -s expand_aliases 放入.bashrc 文件中。也解决不了问题。

仅供参考,这是我的远程命令执行测试代码:

from paramiko import client

class ssh:
    client = None

    def __init__(self, address, username, password, port=22):
        print("Connecting to server.")
        self.client = client.SSHClient()
        self.client.set_missing_host_key_policy(client.AutoAddPolicy())
        self.client.connect(address, port, username=username, password=password, look_for_keys=False)

    def sendCommand(self, command):
        if(self.client):
            stdin, stdout, stderr = self.client.exec_command(command)
            while not stdout.channel.exit_status_ready():
                # Print data when available
                if stdout.channel.recv_ready():
                    alldata = stdout.channel.recv(1024)
                    prevdata = b"1"
                    while prevdata:
                        prevdata = stdout.channel.recv(1024)
                        alldata += prevdata

                    print(str(alldata, "utf8"))
        else:
            print("Connection not opened.")

def main():
    connection = ssh("my_ip", "username", "password", 22)
    connection.sendCommand("dmidecode -t 1") # this doesn't work, "dmidecode command not found"
    connection.sendCommand("pwd") # this works


if __name__ == "__main__":
    main()

对此有什么想法吗?

【问题讨论】:

  • 进展:在 Python 的 paramiko 中,exec_command() 的行为等同于 ssh host_ip command,后者是一个非交互式 shell。
  • 好吧,在我看来,.bashrc 首先验证 shell 是否是交互式的,如果不是,则什么也不做。我的理解是,之后的任何事情都不会被看到/执行。再说一次,您可能想在 serverfault.com 中发送这个问题。
  • 本地定义的函数不会通过 SSH 连接传输到远程主机。

标签: linux bash shell unix sh


【解决方案1】:

实际上,您的标题说明了一切。当您执行ssh login@remote 'my command' 时,根据定义,您的shell 不是交互式的,因为您提供了一个命令。但是,~/.bashrc 仅在您的 shell 交互时由 bash 提供。

当您执行ssh login@remote 'my command' 时,会发生以下情况:

  • 您的计算机首先使用用户“登录”连接到“远程”
  • 然后sshd,在“远程”上运行的 ssh 服务器,使用参数 -c 'my command'(即 bash -c 'my command',因为您使用 bash)执行您的 shell
  • 因为它是用-c 调用的,所以bash 直接执行你的命令而不读取你的启动文件

解决方案?在执行命令之前获取启动文件:

ssh login@remote 'source ~/.bash_aliases; my command'

【讨论】:

  • 感谢您的回答。但是,问题仍然存在。我试过ssh login@remote 'source ~/.bashrc; my command',它仍然说the command is not found
  • @DiLuo 我写了source ~/.bash_aliases。那就是定义您的功能的地方。您的 bashrc 中没有任何内容需要在非交互式 shell 中读取。更糟糕的是:开头有一个命令阻止其执行(请参阅注释“如果不以交互方式运行,则不要执行任何操作”)
  • 你救了我的命。这个.bashrc 文件不是我写的,是系统自带的。非常感谢,您在执行命令之前采购 .bash_aliases 的解决方案是正确的!谢谢!
  • 不客气。最好保持~/.bashrc 原样,而不删除“如果不是交互式则退出”命令,而是填充.bash_aliases。如果您在.bash_aliases 中有很多定义,为了加快远程命令的速度,您可能还想将您需要的功能远程移动到一个特殊文件(例如)~/.ssh_functions 并在.bash_aliases 中获取该文件。然后您的 ssh 命令将变为 ssh login@remote 'source ~/.ssh_functions; my command'
猜你喜欢
  • 1970-01-01
  • 2020-11-24
  • 2011-09-05
  • 2012-10-23
  • 2013-12-23
  • 1970-01-01
  • 2016-04-09
  • 1970-01-01
  • 2011-03-04
相关资源
最近更新 更多