diff options
-rw-r--r-- | Documentation/networking/ip-sysctl.txt | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt index 1b830cac461..dd52d516cb8 100644 --- a/Documentation/networking/ip-sysctl.txt +++ b/Documentation/networking/ip-sysctl.txt | |||
@@ -224,15 +224,14 @@ tcp_fack - BOOLEAN | |||
224 | The value is not used, if tcp_sack is not enabled. | 224 | The value is not used, if tcp_sack is not enabled. |
225 | 225 | ||
226 | tcp_fin_timeout - INTEGER | 226 | tcp_fin_timeout - INTEGER |
227 | Time to hold socket in state FIN-WAIT-2, if it was closed | 227 | The length of time an orphaned (no longer referenced by any |
228 | by our side. Peer can be broken and never close its side, | 228 | application) connection will remain in the FIN_WAIT_2 state |
229 | or even died unexpectedly. Default value is 60sec. | 229 | before it is aborted at the local end. While a perfectly |
230 | Usual value used in 2.2 was 180 seconds, you may restore | 230 | valid "receive only" state for an un-orphaned connection, an |
231 | it, but remember that if your machine is even underloaded WEB server, | 231 | orphaned connection in FIN_WAIT_2 state could otherwise wait |
232 | you risk to overflow memory with kilotons of dead sockets, | 232 | forever for the remote to close its end of the connection. |
233 | FIN-WAIT-2 sockets are less dangerous than FIN-WAIT-1, | 233 | Cf. tcp_max_orphans |
234 | because they eat maximum 1.5K of memory, but they tend | 234 | Default: 60 seconds |
235 | to live longer. Cf. tcp_max_orphans. | ||
236 | 235 | ||
237 | tcp_frto - INTEGER | 236 | tcp_frto - INTEGER |
238 | Enables Forward RTO-Recovery (F-RTO) defined in RFC4138. | 237 | Enables Forward RTO-Recovery (F-RTO) defined in RFC4138. |