如果所有这些都失败了(包括没有timeout命令)，这个shell脚本中的概念将工作:

 #!/bin/bash
 set -u
 ssh $1 "sleep 10 ; uptime" > /tmp/outputfile 2>&1 & PIDssh=$!
 Count=0
 while test $Count -lt 5 && ps -p $PIDssh > /dev/null
 do
    echo -n .
    sleep 1
    Count=$((Count+1))
 done
 echo ""

 if ps -p $PIDssh > /dev/null
 then
    echo "ssh still running, killing it"
    kill -HUP $PIDssh
 else
    echo "Exited"
 fi

"timeout 5 SSH user@machine"对我来说很好。

你可以使用nohup来运行你在“非阻塞模式”下运行的任何东西。你可以继续检查它应该运行的东西是否运行，或者退出。

nohup ./my-script-that-may-take-long-to-finish.sh &
./check-if-previous-script-ran-or-exit.sh

echo "Script ended on Feb 15, 2011, 9:20AM" > /tmp/done.txt

在第二个例子中，你只需要检查文件是否存在。

ssh -o ConnectTimeout=10  <hostName>

10是以秒为单位的时间。此超时仅适用于连接的创建。

使用-o ConnectTimeout和-o BatchMode=yes -o StrictHostKeyChecking=no。

ConnectTimeout使脚本不挂起，BatchMode使脚本不挂起Host unknown, YES添加到known_hosts, StrictHostKeyChecking自动添加指纹。

**** NOTE **** The "StrictHostKeyChecking" was only intended for internal networks where you trust you hosts. Depending on the version of the SSH client, the "Are you sure you want to add your fingerprint" can cause the client to hang indefinitely (mainly old versions running on AIX). Most modern versions do not suffer from this issue. If you have to deal with fingerprints with multiple hosts, I recommend maintaining the known_hosts file with some sort of configuration management tool like puppet/ansible/chef/salt/etc.

你也可以用flag -o ServerAliveInterval=<secs>来连接 因此SSH客户端将每<secs>秒向服务器发送一个空包，只是为了保持连接存活。 在Linux中，也可以在/etc/ssh/ssh_config中全局设置，或在~/.ssh/config中每个用户设置。