https://bugzilla.mindrot.org/show_bug.cgi?id=3067
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
I think you have two options here:
First, you can explicitly shut down multiplexed sessions that have
stalled underlying TCP connection. E.g. I use
for x in ~/.ssh/ctl-* ; do test -r "$x" && ssh -Fnone -Ostop
-oControlPath="$x" dummy ; done
Second, you can set a protocol-level health check to automatically kill
unresponsive sessions. E.g. adding the following to ~/.ssh/config
ServerAliveInterval 2m
ServerAliveCountMax 3
Will terminate any unresponsive connection after six minutes.
--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
I think you have two options here:
First, you can explicitly shut down multiplexed sessions that have
stalled underlying TCP connection. E.g. I use
for x in ~/.ssh/ctl-* ; do test -r "$x" && ssh -Fnone -Ostop
-oControlPath="$x" dummy ; done
Second, you can set a protocol-level health check to automatically kill
unresponsive sessions. E.g. adding the following to ~/.ssh/config
ServerAliveInterval 2m
ServerAliveCountMax 3
Will terminate any unresponsive connection after six minutes.
--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs