| | 130 | * timeouts on client connect (Arne) |
| | 131 | * we have various timeouts in the client - socket timeout, proxy connect timeout, tls handshake timeout |
| | 132 | * master timeout - if connect does not succeed in that time, go to next <remote> |
| | 133 | * goal: only have "master timeout", get rid of individual timeout bits |
| | 134 | * "server poll timeout" -> must receive at least "some answer" in (short) time, to decide whether server is alive at all. Total handshake needs to be much longer (slow CPUs, etc.) --> short timeout to skip over dead servers / dead networks, longer "master timeout" to handle whole setup |
| | 135 | * James: please keep server poll timeout, and keep that short (4s-ish) - the rest could be integrated unless there is a reason to keep them separate |
| | 136 | * feature-ACK: remove all the individual timeouts and replace by "server poll timeout" that is "up to the first packet coming back from the server". If nothing is configured, current default is "0" = "no server poll timeout" - new default: 60 seconds to mimic existing TCP connect timeouts, plus log notice ("if we have multiple remotes and no server-poll-timeout, user experience might be better setting this to a lower value, like 5s"). |
| | 137 | |
| | 138 | * inotify patch from Lev (on list) - feature discussion |
| | 139 | * this is about async authentication plugin (deferred authentication) |
| | 140 | * "response from plugin" is delivered by creation of file |
| | 141 | * currently we stat() in regular intervals -> replace by inotify so system load is lower |
| | 142 | * it's done via a single file descriptor that is added to the master poll() in the event loop which will tell you about arbitrary number of files that are watched |
| | 143 | * portability? |
| | 144 | |
