Brian Dantes, on December 29. 2000, wrote: : 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. Huh? ssh uses standard socket calls to connect to the remote, and the local machine's tcp stack should handle any network related timeouts. The application re-tries the connection for five times before giving up, but it is up to the system call as to how long one attempt takes. It definitely shouldn't hang indefinitely. Have you tried other applications (like telnet, finger) in the same conditions? If they act the same, I'd say your system either has a bug in the TCP code or has been misconfigured somehow. On the other hand, if they timeout correctly, then ssh has set some socket options etc. that the Solaris TCP stack doesn't like. Could you send a verbose (-d 5 would be nice) of a connection attempt which just hangs in these conditions? -- [[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]] [work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl] [SSH Communications Security Corp http://www.ssh.com/]
