| commit | 2738a1494177b3fdf816113c909a68a3467efcc7 | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Sat Jul 08 17:28:09 2006 +0200 |
| committer | Willy Tarreau <w@1wt.eu> | Sun Jul 09 16:22:41 2006 +0200 |
| tree | c6b24e119e2b2c6e805d1cb3c7aa0eeb78c4d11c | |
| parent | 791d66d3634dde12339d4294aff55a1aed7518e3 [diff] |
[MEDIUM] now upon startup, haproxy will warn about missing timeouts. Too many problem reports were caused by missing timeouts. While there has never been any default value since version 1.0, having no timeout is abnormal in networked environments, and will lead to various problems such as CLOSE_WAIT sockets accumulating and nasty things like this. For this reason, it's better to annoy the users until they fix their configs than letting them run buggy configurations.