scp: write stdout: Broken pipe error (Tru64 UNIX)
John P Speno
speno at isc.upenn.edu
Tue Mar 28 02:41:08 EST 2000
I'm working on adding SIA authentication support to OpenSSH for use on
Tru64 UNIX. The authentication bits are working but there's more work to be
done including checking for locked accounts and setting resource limits.
Anyway, most things seem to be working fine except for scp and I'm looking
for a little help. Here's some output:
% scp -v lopan:sl.tar .
Executing: host lopan, user (unspecified), command scp -v -f sl.tar
SSH Version OpenSSH-1.2.3, protocol version 1.5.
Compiled with SSL.
debug: ssh_connect: getuid 4056 geteuid 0 anon 0
debug: Connecting to lopan [165.123.210.223] port 22.
debug: Allocated local port 685.
debug: Connection established.
debug: Remote protocol version 1.5, remote software version OpenSSH-1.2.3
debug: Waiting for server public key.
debug: Received server public key (768 bits) and host key (1024 bits).
debug: Host 'lopan' is known and matches the host key.
debug: Encryption type: 3des
debug: Sent encrypted session key.
debug: Installing crc compensation attack detector.
debug: Received encrypted confirmation.
debug: Doing password authentication.
speno at lopan's password:
debug: Sending command: scp -v -f sl.tar
debug: Entering interactive session.
Cannot find terminal.
Sending file modes: C0600 11530240 sl.tar
sl.tar 4% |*** | 512 KB 00:20 ETAInterrupted system call
11:33am
Write failed flushing stdout buffer.
write stdout: Broken pipe
debug: Transferred: stdin 32, stdout 540758, stderr 27 bytes in 1.3 seconds
debug: Bytes per second: stdin 25.2, stdout 426281.1, stderr 21.3
debug: Exit status -1
I've got a working scp from ssh-1.2.27 around and that still works fine.
Any ideas?
Thanks.
More information about the openssh-unix-dev
mailing list