projects
/
privoxy.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
db26919
)
Regenerate config for 3.0.21 stable
author
Fabian Keil
<fk@fabiankeil.de>
Sat, 2 Mar 2013 14:47:05 +0000
(14:47 +0000)
committer
Fabian Keil
<fk@fabiankeil.de>
Sat, 2 Mar 2013 14:47:05 +0000
(14:47 +0000)
config
patch
|
blob
|
history
diff --git
a/config
b/config
index
8943ecf
..
cda7959
100644
(file)
--- a/
config
+++ b/
config
@@
-1,6
+1,6
@@
-# Sample Configuration File for Privoxy
v3.0.20
+# Sample Configuration File for Privoxy
3.0.21
#
#
-# $Id:
config,v 1.101 2013/01/09 15:19:4
7 fabiankeil Exp $
+# $Id:
p-config.sgml,v 2.97 2013/03/01 17:39:2
7 fabiankeil Exp $
#
# Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
#
#
# Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
#
@@
-1726,7
+1726,7
@@
socket-timeout 300
#
# Default value:
#
#
# Default value:
#
-#
None
+#
128
#
# Effect if unset:
#
#
# Effect if unset:
#
@@
-1762,6
+1762,13
@@
socket-timeout 300
# Obviously using this option only makes sense if you choose a
# limit below the one enforced by the operating system.
#
# Obviously using this option only makes sense if you choose a
# limit below the one enforced by the operating system.
#
+# One most POSIX-compliant systems Privoxy can't properly deal
+# with more than FD_SETSIZE file descriptors at the same time
+# and has to reject connections if the limit is reached. This
+# will likely change in a future version, but currently this
+# limit can't be increased without recompiling Privoxy with a
+# different FD_SETSIZE limit.
+#
# Examples:
#
# max-client-connections 256
# Examples:
#
# max-client-connections 256