current config,1.113,1.114

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

Modified Files:
	config 
Log Message:
Rebuild config file with listen-backlog documentation

Sponsored by: Robert Klemme


Index: config
===================================================================
RCS file: /cvsroot/ijbswa/current/config,v
retrieving revision 1.113
retrieving revision 1.114
diff -C2 -d -r1.113 -r1.114
*** config	8 Jun 2017 13:09:34 -0000	1.113
--- config	26 Jun 2017 12:16:21 -0000	1.114
***************
*** 1906,1910 ****
  #max-client-connections 256
  #
! #  6.10. handle-as-empty-doc-returns-ok
  #  =====================================
  #
--- 1906,1964 ----
  #max-client-connections 256
  #
! #  6.10. listen-backlog
! #  =====================
! #
! #  Specifies:
! #
! #      Connection queue length requested from the operating system.
! #
! #  Type of value:
! #
! #      Number.
! #
! #  Default value:
! #
! #      128
! #
! #  Effect if unset:
! #
! #      A connection queue length of 128 is requested from the
! #      operating system.
! #
! #  Notes:
! #
! #      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.
! #
! #      Increasing the queue length allows Privoxy to accept more
! #      incomming connections that arrive roughly at the same time.
! #
! #      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.
! #
! #      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.
! #
! #      On some platforms you can use "netstat -Lan -p tcp" to see the
! #      effective queue length.
! #
! #      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.
! #
! #  Examples:
! #
! #      listen-backlog 4096
! #
! #listen-backlog -1
! #
! #  6.11. handle-as-empty-doc-returns-ok
  #  =====================================
  #
***************
*** 1944,1948 ****
  #handle-as-empty-doc-returns-ok 1
  #
! #  6.11. enable-compression
  #  =========================
  #
--- 1998,2002 ----
  #handle-as-empty-doc-returns-ok 1
  #
! #  6.12. enable-compression
  #  =========================
  #
***************
*** 1985,1989 ****
  #enable-compression 1
  #
! #  6.12. compression-level
  #  ========================
  #
--- 2039,2043 ----
  #enable-compression 1
  #
! #  6.13. compression-level
  #  ========================
  #
***************
*** 2031,2035 ****
  #compression-level 1
  #
! #  6.13. client-header-order
  #  ==========================
  #
--- 2085,2089 ----
  #compression-level 1
  #
! #  6.14. client-header-order
  #  ==========================
  #
***************
*** 2079,2083 ****
  #
  #
! #  6.14. client-specific-tag
  #  ==========================
  #
--- 2133,2137 ----
  #
  #
! #  6.15. client-specific-tag
  #  ==========================
  #
***************
*** 2144,2148 ****
  #
  #
! #  6.15. client-tag-lifetime
  #  ==========================
  #
--- 2198,2202 ----
  #
  #
! #  6.16. client-tag-lifetime
  #  ==========================
  #
***************
*** 2185,2189 ****
  #
  #
! #  6.16. trust-x-forwarded-for
  #  ============================
  #
--- 2239,2243 ----
  #
  #
! #  6.17. trust-x-forwarded-for
  #  ============================
  #
***************
*** 2240,2244 ****
  #
  #
! #  6.17. receive-buffer-size
  #  ==========================
  #
--- 2294,2298 ----
  #
  #
! #  6.18. receive-buffer-size
  #  ==========================
  #


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