Timeline for How were these Linux TCP default settings decided?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 12:45 | comment | added | OrangeDog | @Robins so does 12 | |
| Jun 2, 2020 at 6:09 | comment | added | Robins | @JoshKupershmidt ... Postgres v13+ now supports tcp_user_timeout. Just FYI. | |
| S Aug 23, 2015 at 14:15 | history | bounty ended | Josh Kupershmidt | ||
| S Aug 23, 2015 at 14:15 | history | notice removed | Josh Kupershmidt | ||
| Aug 23, 2015 at 14:15 | vote | accept | Josh Kupershmidt | ||
| Aug 19, 2015 at 14:27 | comment | added | Josh Kupershmidt | @wnoise actually since Linux 2.6.37 it should also be possible to specify socket option TCP_USER_TIMEOUT as well, instead of setting net.ipv4.tcp_retries2 system-wide. Of course many applications (such as PostgreSQL in my example here) don't support TCP_USER_TIMEOUT yet. | |
| Aug 18, 2015 at 21:16 | comment | added | wnoise | Note that you can change the first three per-connection in client code with the socket options TCP_KEEPIDLE, TCP_KEEPCNT, and TCP_KEEPINTVL. | |
| Aug 18, 2015 at 18:54 | answer | added | wnoise | timeline score: 7 | |
| Aug 17, 2015 at 16:08 | history | tweeted | twitter.com/#!/StackUnix/status/633309414221590528 | ||
| S Aug 17, 2015 at 13:35 | history | bounty started | Josh Kupershmidt | ||
| S Aug 17, 2015 at 13:35 | history | notice added | Josh Kupershmidt | Authoritative reference needed | |
| Aug 12, 2015 at 15:50 | history | edited | Josh Kupershmidt | CC BY-SA 3.0 | tcp_retries2 relevant as well |
| Aug 11, 2015 at 14:47 | review | First posts | |||
| Aug 11, 2015 at 14:56 | |||||
| Aug 11, 2015 at 14:41 | comment | added | Drav Sloan | Some relevant info here... tldp.org/HOWTO/TCP-Keepalive-HOWTO/usingkeepalive.html | |
| Aug 11, 2015 at 14:37 | history | asked | Josh Kupershmidt | CC BY-SA 3.0 |