SCP error status broken on SuSE 9.1?

From: KevJohnP (nospam_at_nowhere.com)
Date: 07/27/04


Date: Tue, 27 Jul 2004 13:11:07 +0100

I have a program that calls scp to transfer a file to a
pre-authenticated user. The problem is that scp is copying the file
fine but giving back inconsistent return codes - mostly success (0) but
occassionally -1 with no information any different in the -v debug
output. In all cases the file has transferred fine.

The platform is SuSE 9.1 client transferring to a Solaris9 X86 server.

Anyone seen this before?? Debug output below.

TIA

The file concerned contains a text string "Some text" with a \n and
appears fine on the destination system.

debug1: Sending command: scp -v -t /tmp/BillImgArchSec.pl.22976
Sending file modes: C0644 10 BillImgArchSec.pl.22976
BillImgArchSec.pl.22976 100% 10 0.0KB/s 00:00
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
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0

debug1: Sending command: scp -v -t /tmp/BillImgArchSec.pl.23294
Sending file modes: C0644 10 BillImgArchSec.pl.23294
BillImgArchSec.pl.23294 100% 10 0.0KB/s 00:00
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status -1