<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 02.06.2016 10:09, thierry bordaz wrote: </div> <blockquote cite="mid:574FE9B6.2040809@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 06/02/2016 09:48 AM, Martin Basti wrote: </div> <blockquote cite="mid:a9b5fda5-de58-fbae-6c36-2e45e40b9d8a@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 31.05.2016 17:10, Stanislav Laznicka wrote: </div> <blockquote cite="mid:655db353-b7f2-cee7-3cff-2635ee6bd523@redhat.com" type="cite">Hello, This is a fix to <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://fedorahosted.org/freeipa/ticket/5383">https://fedorahosted.org/freeipa/ticket/5383</a>. From the comments I am not sure if nsslapd-idletimeout should be reduced as well. If so, could you please propose a value that you find reasonable? Thanks, Standa <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> It looks that only ioblocktimeout is safe to change and we should not change the second attribute, Thierry can you confirm this? Martin^2 </blockquote> The patch looks ok to me. It is safe to tune idletimeout as well but here it does not bring real benefit. The patch leaves idletimeout to the default value that is no close on idle connection. ioblock is set to 10s that is in a good range of values (DS team recommended 10-30s). Note that ioblock is sensitive for slow ldap client. If a client is not able to read fast enough, the server will close the connection. This can happen for example if a client did a large SRCH and is processing slowly the received entries. thierry </blockquote> ACK, works for me Pushed to master: e9f0e9d8fafb35acf0adbd99d40c16edf510ff9f </body> </html>