5

As said, an image is worth a thousand words:

enter image description here

This blank line is weird.

SSH works correctly.

Some verbose mode shows me this:

enter image description here

I just... scp never gave up on me. Looks like it did today.

4
  • I wanted to add the wtf tag, but don't have enough reputation. Jan 7, 2013 at 16:33
  • Totally worth that tag! Jan 7, 2013 at 16:39
  • Could the line be the progress meter? I know it is normally ===> but...
    – terdon
    Jan 7, 2013 at 16:56
  • @terdon yeah, this is normally ===>. Maybe it's a "starting to write but failed" line... dunno. Jan 7, 2013 at 17:12

3 Answers 3

3

The issue was that I added some fun stuff in the remote .bashrc, namely some cowsay + fortune.

This screwed everything up. Removing it, everything worked flawlessly again.

1

For those stumbling on this thread as I did, but who want to preserve their fortune telling cow friends - Add this to the head of your .bashrc.

# If not running interactively, don't do anything                                                                                                
# prevents bashrc from breaking non-interactive commands                                                                                             
# like SCP                                                                                                                                       
case $- in                                                                                                                                       
    *i*) ;;                                                                                                                                      
    *) return;;                                                                                                                                  
esac 

This will check for interactivity and not run your .bashrc for non-interactive shells - such as the SCP case above.

0

"Note that scp clients do not know how to handle certain URI characters - therefore the filename reported in the status is mangled to remove bad characters with "_" (underscores). This is only for the status report and has no affect on the target filename."

From this page (I googled "scp sink underscore" and looked at the first link. Others may be more explicit)

You may want to try another LC_LANG : LC_LANG=C scp .......... (and try others, until display is correctly showing the filename).

0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .