bugzilla-daemon at mindrot.org
2005-Apr-06 18:50 UTC
[Bug 813] Scp to s Solaris 9 box gives "exit status 1" although file is delivered.
http://bugzilla.mindrot.org/show_bug.cgi?id=813 ------- Additional Comments From alex at milivojevic.org 2005-04-07 04:50 ------- I was doing some testing, and the strange thing is that SunSSH server gives wrong exit status only when using newer versions of openssh on the client side. For example, Red Hat 7.3 as client (openssh 3.1) is OK Fedora Core / RHEL4 as client (openssh 3.9) gives error Fedora devel as client (openssh 4.0) gives error Unlike Darren's results, the results I got when testing were consistent (as in "every single time"). OpenSSH 3.1 on client side always works correctly. OpenSSH 3.9 and newer on client side always gives non-zero exit status (but file transfer itself is OK). Could it be that something changed in OpenSSH that triggers this behaviour in SunSSH server? Maybe OpenSSH isn't as innocent as it might look on a first glance? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Seemingly Similar Threads
- [Bug 813] Scp to s Solaris 9 box gives "exit status 1" although file is delivered.
- [Bug 905] scp exit status is -1 instead of 0
- FYI Incompatibilities between recent versions of OpenSSH and Sun SSH
- [PATCH] Drop fine-grained privileges on Illumos/Solaris
- [Bug 369] Inconsistant exit status from scp