SUMMARY: scp weirdness

Thanks to Alex Ugolini for pointing the below out,

from: http://www.openssh.com/faq.html#2.9

        2.9 - sftp/scp fails at connection, but ssh is OK.
        sftp and/or scp may fail at connection time if you
        have shell initialization (.profile, .bashrc, .cshrc,
        etc) which produces output for non-interactive sessions.
        This output confuses the sftp/scp client.  You can
        verify if your shell is doing this by executing:

                ssh yourhost /usr/bin/true

        If the above command produces any output, then you
        need to modify your shell initialization.

I have the below towards the end of my .bashrc...

if [ x$TERM = xdumb ];
then
        echo "Resetting terminal type from dumb to vt100..."
        export TERM=vt100
fi

...took it out and scp works.


- Mike

ftp.patriots.net --great Solaris sparc/x86 packages.
www.ondruska.com --popular Solaris x86 packages.


---------- Original message ----------

$ scp -p mike@192.168.1.2:/home/mike/file1.txt .
mike@192.168.1.2's password:
Resetting terminal type from dumb to vt100...

The file1.txt never transfer, instead the server spawn another sshd
process and seems to execute the .bashrc instead of transfering the
file.  netstat shows the connection still established, which is odd,
after 24 hours (shouldn't it timeout already?)

I'm running openssh3.5p1 --any clues to the oddness of scp???

Thanks.


- Mike

ftp.patriots.net --great Solaris sparc/x86 packages.
www.ondruska.com --popular Solaris x86 packages.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers