Difference between revisions of "Configuring idle timeout for shell"
(Created page with "=Configuring idle timeout for shell= We can configure idle timeout for bash by following steps: #Create file named '<tt>/etc/profile.d/autologout.sh</tt>' #Add following con...") |
m |
||
| Line 1: | Line 1: | ||
<yambe:breadcrumb self="Configuring idle timeout for shell">Shell configuration|Shell configuration</yambe:breadcrumb> | |||
=Configuring idle timeout for shell= | =Configuring idle timeout for shell= | ||
| Line 16: | Line 17: | ||
Technique has been learned from http://www.cyberciti.biz/faq/linux-unix-login-bash-shell-force-time-outs/ | Technique has been learned from http://www.cyberciti.biz/faq/linux-unix-login-bash-shell-force-time-outs/ | ||
<yambe:breadcrumb self="Configuring idle timeout for shell">Shell configuration|Shell configuration</yambe:breadcrumb> | |||
Revision as of 05:48, 21 August 2018
<yambe:breadcrumb self="Configuring idle timeout for shell">Shell configuration|Shell configuration</yambe:breadcrumb>
Configuring idle timeout for shell
We can configure idle timeout for bash by following steps:
- Create file named '/etc/profile.d/autologout.sh'
- Add following contents to file:
- TMOUT=300
- readonly TMOUT
- export TMOUT
- chmod +x /etc/profile.d/autologout.sh'
Note: Do not make mistakes in this file like adding 'exit 0'. All /etc/profile.d scripts are run directly from new shell which is getting spawned. Making mistakes in profile.d scripts may make shell inaccessible. Hence never experiment with new profile.d scripts on servers on which you have only remote access, like hosting services, cloud, etc. In case some mistake is already done you can refer to Deleting shell start-up scripts remotely without executing them, to make system work again.
Technique has been learned from http://www.cyberciti.biz/faq/linux-unix-login-bash-shell-force-time-outs/
<yambe:breadcrumb self="Configuring idle timeout for shell">Shell configuration|Shell configuration</yambe:breadcrumb>
