From e994f44d9c5a0c61bf6b824720be67476d4487ed Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Thu, 25 Mar 2021 12:52:00 +0100 Subject: [PATCH] Update max-client-connections's description On modern systems other than Windows Privoxy should use poll() in which case the FD_SETSIZE value isn't releveant. --- doc/source/p-config.sgml | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index bb93a806..042400ef 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3184,10 +3184,15 @@ forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010 One most POSIX-compliant systems &my-app; 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 &my-app; with a different FD_SETSIZE limit. + more than FD_SETSIZE file descriptors if &my-app; has been configured + to use select() and has to reject connections if the limit is reached. + When using select() this limit therefore can't be increased without + recompiling &my-app; with a different FD_SETSIZE limit unless &my-app; + is running on Windows with _WIN32 defined. + + + When &my-app; has been configured to use poll() the FD_SETSIZE limit + does not apply. -- 2.49.0