When I type scp file1 [email protected]:file2 into the command prompt, I get the message
Can't open display
Can't open display
Can't open display
Can't open display
Can't open display
file1 100% 589KB 589.0KB/s 00:00
And then I wait for about 10 seconds, before the scp returns to the command line. This does not happen with ssh, only with scp. I am using Fedora 18.
Your profile scripts probably have some commands that expect an interactive session with a terminal emulation. And they fail when executed in a non-interactive scp session.
For example, if you are using bash, such commands should be moved from .bashrc script to .bash_profile.
Or use TERM or PS1 environment variable or similar trick to skip those commands for a non-interactive session.
# If running interactively, then:
if [ "$PS1" ]; then
#### Alex's funky commands might go here <------
/usr/bin/ssh-agent &
# If this is an xterm set the title to user@host:dir
case $TERM in
xterm*)
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"'
#### Alex's funky commands might also go here if they apply to xterm sessions <------
;;
*)
;;
esac
fi
This will not evaluate if you use scp to copy a file, but will if you start an interactive session.
(The sample code is by @Criggie)
.bashrc that were causing this to happen.
xrandr commands intended to detect which screens are present, and to arrange them in an appropriate order.
scp used a special sftp subsystem rather than doing a regular SSH login.
scp does not use SFTP subsystem. 2) Even sftp would suffer the same problem - SFTP still runs over SSH login.
scp file1 [email protected]:/home/user/file2?