Timeline for How long is a TCP local socket address that has been bound unavailable after closing?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2018 at 22:44 | comment | added | Philippe Gachoud | your speculations were interesting! just flag them as that with a title instead of removing them, it gives ways to search for the reason why! | |
| S Dec 26, 2018 at 13:32 | history | suggested | Philippe Gachoud | CC BY-SA 4.0 | added complete path of tcp_tw_recycle |
| Dec 26, 2018 at 12:12 | review | Suggested edits | |||
| S Dec 26, 2018 at 13:32 | |||||
| Jul 22, 2011 at 19:17 | history | edited | user732 | CC BY-SA 3.0 | Remove some speculation, replace it with factual information. |
| Jul 22, 2011 at 14:07 | comment | added | Tom Anderson | I understand (roughly) what the purpose of the period of unavailability is. What i would like to know is exactly how long that period is on Linux, and how it can be changed. The problem with a number from a Wikipedia page about TCP is that it is necessarily a generalised value, and not something that is definitely true of my specific platform. | |
| Jul 22, 2011 at 13:30 | history | answered | user732 | CC BY-SA 3.0 |