SCP在.bashrc中回显时不起作用？
我在Fedora有两个用户：
- 迩
- 根（相当明显！）
我的用户Wani的.bashrc的内容是：
# .bashrc echo "Hello" # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi # User specific aliases and functions 现在login到root后，input以下命令：
[root@Dell Wani]# touch try.txt [root@Dell Wani]# service sshd start [root@Dell Wani]# scp try.txt Wani@localhost:~/ Wani@localhost's password: Hello [root@Dell Wani]#
现在我login到Wani，input：
[Wani@Dell ~]$ cat try.txt cat: try.txt: No such file or directory [Wani@Dell ~]$
现在我再次login到root并使用-v键入相同的命令：
[root@Dell Wani]# scp -v morph.log Wani@localhost: Executing: program /usr/bin/ssh host localhost, user Wani, command scp -v -t -- . OpenSSH_5.6p1, OpenSSL 1.0.0j-fips 10 May 2012 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6 debug1: match: OpenSSH_5.6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi- with-mic,password debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_0' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_0' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: password Wani@localhost's password: debug1: Authentication succeeded (password). Authenticated to localhost ([127.0.0.1]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env XMODIFIERS = @im=none debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t -- . Hello [root@Dell Wani]# debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK Transferred: sent 1664, received 1976 bytes, in 0.1 seconds Bytes per second: sent 22961.5, received 27266.8 debug1: Exit status 0
（和我按Enter键后）
[root@Dell Wani]#
任何人都可以请说一说这里发生了什么？ 为什么该文件不能从根目录复制到Wani？
在.bashrc使用echo会破坏scp ，因为scp希望通过stdin / stdout通道看到它的协议数据。 有关此问题的更多讨论，请参见https://bugzilla.redhat.com/show_bug.cgi?id=20527 。
有几个解决方法可用：
- “互动”标志上的条件（例如，由tripleeebuild议的
case $- in *i*） - 使用
tty实用程序检测交互式shell（例如，if tty > /dev/null或者if [ -t 0 ]） - 检查
$SSH_TTY的值
我想你应该使用哪一个为你工作。 不幸的是，我不知道什么是最好的（最便携/最可靠的）选项。
要添加到nneonneo的选项，您也可以使用交互式标志
if [[ $- =~ "i" ]]
我认为这可能是bash中最清晰的方式。
这对我有用，
在.bashrc添加第一行为：
if [ -z "$PS1" ]; then return fi
https://superuser.com/questions/690735/can-i-tell-if-im-in-an-scp-session-in-my-bashrc
在.bashrc ，使用STDERR作为输出：
echo "# Important Notice" >&2
更新：不要使用它！ 最近我们遇到了一个问题，由于在.bashrc对STDERR的echo ，（闭源）工具失败了。 该工具（使用rcp ）在STDOUT和STDERR上都没有输出。 当它得到回声时卡住了。 获得的经验：为人类和机器（脚本）创build单独的账户，或者停止通过.bashrc敲击。
默认的 Ubuntu .bashrc包含下面的代码片段，它已经处理了这个问题：
# If not running interactively, don't do anything case $- in *i*) ;; *) return;; esac
nneonneo的解决scheme也为我工作。 但是由于我的默认shell是TCSH，所以我不得不按如下方式（在.tcshrc中）修改这个修补程序：
if ( $?SSH_TTY ) then exec /bin/bash endif
只是想我会分享给大家的好处。
