current/doc/source p-config.sgml,2.126,2.127

Update of /cvsroot/ijbswa/current/doc/source
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv21867/doc/source

Modified Files:
	p-config.sgml 
Log Message:
Document the listen-backlog directive

Sponsored by: Robert Klemme


Index: p-config.sgml
===================================================================
RCS file: /cvsroot/ijbswa/current/doc/source/p-config.sgml,v
retrieving revision 2.126
retrieving revision 2.127
diff -C2 -d -r2.126 -r2.127
*** p-config.sgml	29 May 2017 10:02:37 -0000	2.126
--- p-config.sgml	26 Jun 2017 12:14:38 -0000	2.127
***************
*** 3177,3180 ****
--- 3177,3259 ----
  
  
+ <sect3 renderas="sect4" id="listen-backlog"><title>listen-backlog</title>
+ <variablelist>
+  <varlistentry>
+   <term>Specifies:</term>
+   <listitem>
+    <para>
+     Connection queue length requested from the operating system.
+    </para>
+   </listitem>
+  </varlistentry>
+  <varlistentry>
+   <term>Type of value:</term>
+   <listitem>
+    <para>
+     <replaceable>Number.</replaceable>
+    </para>
+   </listitem>
+  </varlistentry>
+  <varlistentry>
+   <term>Default value:</term>
+   <listitem>
+    <para>128</para>
+   </listitem>
+  </varlistentry>
+  <varlistentry>
+   <term>Effect if unset:</term>
+   <listitem>
+    <para>
+     A connection queue length of 128 is requested from the operating system.
+    </para>
+   </listitem>
+  </varlistentry>
+  <varlistentry>
+   <term>Notes:</term>
+   <listitem>
+    <para>
+     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.
+    </para>
+    <para>
+     Increasing the queue length allows Privoxy to accept more
+     incomming connections that arrive roughly at the same time.
+    </para>
+    <para>
+     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.
+    </para>
+    <para>
+     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.
+    </para>
+    <para>
+     On some platforms you can use "netstat -Lan -p tcp" to see the effective
+     queue length.
+    </para>
+    <para>
+     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.
+    </para>
+   </listitem>
+  </varlistentry>
+  <varlistentry>
+   <term>Examples:</term>
+   <listitem>
+    <para>
+     listen-backlog 4096
+    </para>
+   </listitem>
+  </varlistentry>
+ </variablelist>
+ <![%config-file;[<literallayout>@@#listen-backlog -1</literallayout>]]>
+ </sect3>
+ 
+ 
  <sect3 renderas="sect4" id="handle-as-empty-doc-returns-ok"><title>handle-as-empty-doc-returns-ok</title>
  <variablelist>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot