From b007fbc564941cc5fcc22f356cf5f9a6433aa932 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sat, 2 Jan 2021 14:37:24 +0100 Subject: [PATCH] Bring back "--with-fdsetsize" now that select() is supported again This reverts commit d2a6fcf8b923dc9f81b03417ede4d44f0beb03e0. --- configure.in | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/configure.in b/configure.in index c6276434..91d8128d 100644 --- a/configure.in +++ b/configure.in @@ -480,6 +480,27 @@ fi AC_SUBST(PTHREAD_ONLY) +dnl ================================================================= +dnl On most platforms select() does not support fd numbers above +dnl FD_SETSIZE, as a result Privoxy can't handle more than +dnl approximately FD_SETSIZE/2 client connections. +dnl On some platforms the value can be changed at compile time, +dnl on others it's hardcoded and requires recompilation of the OS. +dnl Only relevant if select() is actually being used. +dnl ================================================================= +AC_ARG_WITH(fdsetsize, + [ --with-fdsetsize=n Optimistically redefine FD_SETSIZE with the intend to change the number of connections Privoxy can handle. Dangerous if the platform doesn't support this. Pointless if Privoxy can use poll() instead of select().], + [ + if test "x$withval" != "xyes"; then + AC_DEFINE_UNQUOTED(FD_SETSIZE,$with_fdsetsize,[Relevant for select(). Not honoured by all OS.]) + echo "Redefining FD_SETSIZE to $with_fdsetsize." + AC_MSG_WARN(On platforms that don't support FD_SETSIZE redefinition it may cause memory corruption.) + else + AC_MSG_ERROR(--with-fdsetsize used without value) + fi + ] +) + dnl ================================================================= dnl Support for thread-safe versions of gethostbyaddr, gethostbyname, dnl gmtime and localtime -- 2.39.2