Patch to fix the 255 status code problem

[tim.mann at bt.com]

Hi,

Thanks for your reply.

I'm having problems with  a dataguard deployment using Oracle 8.1.7.4. I
found an article on Metalink which seem to explain the problem I was
having. It states that with openssh (on Solaris) it returns status code
255 for a successful execution and this is interpreted by dataguard as a
connection failure. 

When I run ssh on the command line everything is fine.

The other solution the article states is to use SSH1 instead.

Regards,

Tim

-----Original Message-----
From: Daniel Kahn Gillmor [mailto:dkg-openssh.com at fifthhorseman.net] 
Sent: 31 January 2007 16:40
To: Mann,TJ,Tim,XWK3 R
Cc: openssh-unix-dev at mindrot.org
Subject: Re: Patch to fix the 255 status code problem

At 2007-01-31 15:53, tim.mann at bt.com said:

> Currently using openssh-4.5p1 on Solaris 8 in conjunction with Oracle 
> 8i dataguard. Is there a patch available to prevent ssh returning 
> status code 255 for a successful execution of a remote 
> connection/command.

I believe it should already do what you need.  the man page [0] says:

  ssh exits with the exit status of the remote command or with 255 if
  an error occurred.

Can you provide more details about the problem you're having?  The
behavior it sounds like you want is already present on my setup here
(openssh 4.2p1 and 3.8.1p1 on linux 2.6).  My prompt shows the return
value of the previous command:

[0 dkg at baboon ~]$ ssh gorilla true
[0 dkg at baboon ~]$ ssh gorilla false
[1 dkg at baboon ~]$ 

hth,

	--dkg

[0] http://www.openbsd.org/cgi-bin/man.cgi?query=ssh