I've seen various posts here about this problem - but no answers.
I'm running SSH2 2.4.0 under Solaris 2.8 in a cron job script, and the
script hangs indefinitely when the server it's trying to reach is
completely unavailable for various network reasons.

I was really hoping for a timeout parameter in the client that would
force it to abandon the connection attempt after a specified amount
of time. I'm frankly amazed that no provision was made for this
feature.

A few have suggested setting my own alarm around the call to ssh -
but that is unacceptable, because the command I am executing
(assuming the connection is successful) could take an undetermined
amount of time to complete. I don't want to timeout my remote
command - just the connection attempt.

Is there anyway to achieve this? Is this a known bug?

Direct replies would be appreciated.

Brian Dantes
[EMAIL PROTECTED]


Reply via email to