timed out waiting for input: auto-logout

The ssh "timed out waiting for input: auto-logout" messages is generated by ssh upon reaching a auto-logout after an inactivity time specified by the TMOUT environment variable. If this variable is not set your session will not be auto-logged out due to inactivity. If the environment variable is set, your session will be automatically closed/logged out after the amount of seconds specified by the TMOUT variable.

To see if your auto-logout variable is set and/or see what it is set to issue the following command:
 $ echo $TMOUT

Often this value is defined in /etc/profile (globally) or your user‘s profile (~/.profile or ~/.bash_profile).

To alter the auto-logout amount, set the TMOUT environment variable accordingly:
* TMOUT=600   #set an auto-logout timeout for 10 minutes
* TMOUT=1200  #set an auto-logout timeout for 20 minutes
* TMOUT=   #turn off auto-logout (user session will not auto-logout due to session inactivity)

This value can be set globally (e.g. TMOUT=1200) in the /etc/profile file; however, each user can override the value by setting the TMOUT variable in their personal profile file (~/.profile or ~/.bash_profile). To do this simply set the TMOUT variable as you like in your profile file.

Dont forget to source the file you changed to get the settings to take effect immediately or log out and log back in.
e.g:  source  /etc/profile

时间: 2024-10-09 00:16:11

timed out waiting for input: auto-logout的相关文章

终端 timed out waiting for input: auto-logout解决!

问题: 在ssh密钥连接情况下,一定时间不输入,则自动退出. $timed out waiting for input: auto-logout超时等待输入:自动注销 一开始感觉和ssh检测机制有关系, 1.ssh超时 设置服务器向SSH客户端连接会话发送频率和时间.#vi /etc/ssh/sshd_config,添加如下两行 # 启用客户端活动检查,每60秒检查一次,3次不活动断开连接 ClientAliveInterval 60ClientAliveCountMax 3 # ClientA

timed out waiting for device to boot,unable to boot the iOS Simulator

平常工作中的关于XCode出现bug解决之后一定要做个记录,要不下次真的再遇到只记得遇到过,怎么解决的是真忘了. COM+R运行xcode之后,模拟器半天没反应,待会会出现这个下面图1这样的弹框,另外timed out waiting for device to boot这句话的一个弹框,不过问题解决了这个图2的弹框没有及时截图,只记得这句话. 出现这种问题大部分都是在升级XCode或者删除XCode再安装新的之后,会遇到的问题,我安装删除循环了N遍,问题还是没解决,网上找了半天也都没有解决,最

DHCP request error:Timed out waiting for dhcpcd to start【转】

本文转载自:http://blog.csdn.net/zvivi521/article/details/9166899 [init.svc.dhcpcd_eth0]: [stopped] I/ServiceManager( 2040): Waiting for service android.tvs.daemon...D/NetUtils( 1412): android_net_utils_runDhcpCommon, result:-1E/EthernetDataTracker( 1412):

MessagingTimeout: Timed out waiting for a reply to message ID

l3中出现大量消息超时错误,对网络的操作各种异常. 报错如下: 2016-02-25 05:54:59.886 15110 ERROR neutron.agent.l3.agent [req-db9207e6-9270-4f23-8c19-0d91d20cc6fb ] Failed synchronizing routers due to RPC error2016-02-25 05:54:59.886 15110 TRACE neutron.agent.l3.agent Traceback (

OpenStack报错:MessagingTimeout: Timed out waiting for a reply to message ID

L3.agent中出现大量消息超时错误,对网络的操作各种异常. 报错如下: 2018-09-24 05:54:59.886 15110 ERROR neutron.agent.l3.agent [req-db9207e6-9270-4f23-8c19-0d91d20cc6fb ] Failed synchronizing routers due to RPC error 2018-09-24 05:54:59.886 15110 TRACE neutron.agent.l3.agent Trac

Xcode Coule not launch "aaa" press launch failed:timed out waiting for app launch

遇见这个问题 可能是 由于 runapp 的时候设置里面 设置为release了. 解决办法是:见图 build configuration 设置成 debug 状态就OK了. 要是上面的不行就试一下 stackoverflow上面的大神方案: 1.itounes 退出 2.手机 重启 然后 卸了app 3.Xcode 重启  clean 一下 4.重新运行 希望能够帮助 一些人.

(adhoc) process launch failed: timed out waiting for app to launch

I had a similar issue when trying to debug an App with Ad-Hoc provisioning... Check which provisioning you're using, it seems ad-hoc provisioning cannot be used for debugging. EDIT In fact, it seems only development provisioning profiles are Ok for d

kubeadm join 超时报错 error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition

解决: swapoff -a kubeadm reset systemctl daemon-reload systemctl restart kubelet iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X 原文地址:https://www.cnblogs.com/winstom/p/11840732.html

kubeadm join 超时 uploading crisocket: timed out waiting for the condition

swapoff -a # will turn off the swap kubeadm reset systemctl daemon-reload systemctl restart kubelet iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X # will reset iptables 原文地址:https://www.cnblogs.com/zhaoji