Re: scp fails without a warning.

[SZABO Gergely <gergely dot szabo at knorr-bremse dot com>]

Wiles, Dale L. (NE <Dale.Wiles <at> gd-ais.com> writes:

> 
> I updated cygwin yesterday (10/12/10) and rebooted my Windows XP (SP3) box. 
Now, when I use scp from a Red Hat
> 5.5 box to my Windows box, scp quietly fails.
> 
> If I run (from Red Hat) "scp uname <at> windowsbox:file .", I'm prompted for
my password.  I type it in and then, a
> moment later, scp exits.  No data gets transferred and there is no error
messages.  If I type in a garbage file
> name, I get the same results.  There is no error message.
> 
> If I run "sftp uname <at> windowsbox:file ." I'm prompted for my password and
the file transfers normally. 
> Unfortunately I need a recursive copy.
> 
> I can also ssh into my windows box with no problem.
> 
> /var/log/sshd.log exists, but is empty.
> 


At least, could you check scp's exit code?
$ scp ....
$ echo $?

If it's nonzero, you could produce the error message yourself:
$ scp ... || echo "scp failed"

Not that it fixes scp... :-(
Does MidnightCommander's Shell-link panel fail too?

Best regards
Gergely



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple