OpenSSH solaris: bad return code after exec of remote command
markus at openbsd.org
Wed Oct 10 20:37:23 EST 2001
On Wed, Oct 10, 2001 at 11:09:17AM +0100, Matthew Seaman wrote:
> i) SSH2 protocol
> ii) Using a forced command
> iii) No stdin on the client --- ie. using `ssh -n' or
> `ssh host commands </dev/null'.
i don't see how forced commands should change things here.
but, yes there are issues with getting the return code from the
child in ssh2.
for i in 4 7 44 77; do
ssh -n host exit $i
print for you?
More information about the openssh-unix-dev