+ <div class="SECT3">
+ <h4 class="SECT3"><a name="LISTEN-BACKLOG" id=
+ "LISTEN-BACKLOG">7.6.10. listen-backlog</a></h4>
+ <div class="VARIABLELIST">
+ <dl>
+ <dt>Specifies:</dt>
+ <dd>
+ <p>Connection queue length requested from the operating
+ system.</p>
+ </dd>
+ <dt>Type of value:</dt>
+ <dd>
+ <p><tt class="REPLACEABLE"><i>Number.</i></tt></p>
+ </dd>
+ <dt>Default value:</dt>
+ <dd>
+ <p>128</p>
+ </dd>
+ <dt>Effect if unset:</dt>
+ <dd>
+ <p>A connection queue length of 128 is requested from the
+ operating system.</p>
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ <p>Under high load incoming connection may queue up before
+ Privoxy gets around to serve them. The queue length is limitted
+ by the operating system. Once the queue is full, additional
+ connections are dropped before Privoxy can accept and serve
+ them.</p>
+ <p>Increasing the queue length allows Privoxy to accept more
+ incomming connections that arrive roughly at the same time.</p>
+ <p>Note that Privoxy can only request a certain queue length,
+ whether or not the requested length is actually used depends on
+ the operating system which may use a different length
+ instead.</p>
+ <p>On many operating systems a limit of -1 can be specified to
+ instruct the operating system to use the maximum queue length
+ allowed. Check the listen man page to see if your platform
+ allows this.</p>
+ <p>On some platforms you can use "netstat -Lan -p tcp" to see
+ the effective queue length.</p>
+ <p>Effectively using a value above 128 usually requires
+ changing the system configuration as well. On FreeBSD-based
+ system the limit is controlled by the kern.ipc.soacceptqueue
+ sysctl.</p>
+ </dd>
+ <dt>Examples:</dt>
+ <dd>
+ <p>listen-backlog 4096</p>
+ </dd>
+ </dl>
+ </div>
+ </div>