From: Nick Porter Date: Tue, 3 Dec 2024 11:11:42 +0000 (+0000) Subject: Update sample mschap config to reflect slab parameters X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ba825ebb4f005d376712349e59ef285328026ab7;p=thirdparty%2Ffreeradius-server.git Update sample mschap config to reflect slab parameters --- diff --git a/raddb/mods-available/mschap b/raddb/mods-available/mschap index 4991a3b136a..721b9b378b4 100644 --- a/raddb/mods-available/mschap +++ b/raddb/mods-available/mschap @@ -193,115 +193,32 @@ mschap { # the backend, and retry authentication with that username. # # retry_with_normalised_username = no - } - - # - # .Pool - # - # TIP: Information for the winbind connection pool. The - # configuration items below are the same for all modules - # which use the connection pool. - # - pool { - # - # start:: Connections to create during module instantiation. - # - # If the server cannot create specified number of - # connections during instantiation it will exit. - # Set to `0` to allow the server to start without the - # external service being available. - # - start = 0 - - # - # min:: Minimum number of connections to keep open. - # - min = 0 - - # - # max:: Maximum number of connections. - # - # If these connections are all in use and a new one - # is requested, the request will NOT get a connection. - # - # Setting `max` to *LESS* than the number of threads means - # that some threads may starve, and you will see errors - # like _No connections available and at max connection limit_. - # - # Setting `max` to MORE than the number of threads means - # that there are more connections than necessary. - # - # If `max` is not specified, then it defaults to the number - # of workers configured. - # -# max = - - # - # spare:: Spare connections to be left idle. - # - # NOTE: Idle connections WILL be closed if `idle_timeout` - # is set. This should be less than or equal to `max` above. - # - spare = 1 # - # uses:: Number of uses before the connection is closed. + # .Reusable Handles # - # 0 means "infinite" + # Reusable connection handles are allocated in blocks. These + # parameters allow for tuning how that is done. # - uses = 0 + reuse { + # + # min:: The minimum number of connection handles to + # keep allocated + # +# min = 10 - # - # retry_delay:: - # - # The number of seconds to wait after the server tries - # to open a connection, and fails. During this time, - # no new connections will be opened. - # - retry_delay = 30 + # + # max:: The maximum number of reusable connection + # handles to allocate. + # +# max = 100 - # - # lifetime:: - # - # The lifetime (in seconds) of the connection. - # - # NOTE: A setting of 0 means infinite (no limit). - # - lifetime = 86400 - - # - # cleanup_interval:: - # - # The pool is checked for free connections every - # `cleanup_interval`. If there are free connections, - # then one of them is closed. - # - cleanup_interval = 300 - - # - # idle_timeout:: - # - # The idle timeout (in seconds). A connection which is - # unused for this length of time will be closed. - # - # NOTE: A setting of `0` means infinite (no timeout). - # - idle_timeout = 600 - - # - # [NOTE] - # ==== - # All configuration settings are enforced. If a - # connection is closed because of `idle_timeout`, - # `uses`, or `lifetime`, then the total number of - # connections MAY fall below `min`. When that - # happens, it will open a new connection. It will - # also log a WARNING message. - # - # The solution is to either lower the `min` connections, - # or increase lifetime/idle_timeout. - # ==== - # + # + # cleanup_interval:: How often to free un-used + # connection handles. + # +# cleanup_interval = 30s + } } #