On 10/04/2013 03:58 PM, olli hauer wrote:
On 2013-10-05 00:34, ToddAndMargo wrote:
On 10/04/2013 03:12 PM, olli hauer wrote:
On 2013-10-04 23:13, ToddAndMargo wrote:
Hi All,
I use an ssh terminal shell to an FC 19 computer
to run mainenance over the network.
ssh -l todd -t -X -p 22 192.168.255.102
I have noticed if I let the terminal set too long
without activity, that the terminal won't accept
keyboard input. I have to "X" it out and start
a new terminal.
Have I missed an inactivity setting or something?
Many thanks,
-T
on the target system set the following parameters
(if they exists in FC19) and restart sshd before
connecting again
$ grep ClientAlive /etc/ssh/sshd_config
ClientAliveInterval 10
ClientAliveCountMax 3
Hi Olli,
I found a
TCPKeepAlive yes
Is that a better parameter?
If the parameters I ClientAlive... are not aviable yes.
The TCPKeepAlive (older) is outside from SSH and ClientAlive... (newer) inside
the SSH tunnel.
So if you have a strict firewall which permitts SSHv2 to a customer and nothing
else TCPKeepAlive is useless.
Sorry to pointing you now to another OS site but here you can find a good
explanation in the online manpage
http://www.freebsd.org/cgi/man.cgi?query=sshd_config&manpath=FreeBSD+9.2-RELEASE
Hi Olli,
Thank you!
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
