Add two more reasons why ssld_count>1 can be useful: bugs and fd limits.

diff --git a/doc/example.conf b/doc/example.conf
index ada53790c4dd755088a24f99641d19343b2b76a3..b00a29f911bce9234f731f3d003e762090977c8a 100755 (executable)
--- a/doc/example.conf
+++ b/doc/example.conf
@@ -56,8 +56,11 @@ serverinfo {
        /* ssl_dh_params: DH parameters, generate with openssl dhparam -out dh.pem 1024 */
        ssl_dh_params = "etc/dh.pem";
 
-       /* ssld_count: number of ssld processes you want to start, if you have a really busy 
-        * server, using N-1 where N is the number of cpu/cpu cores you have might be useful
+       /* ssld_count: number of ssld processes you want to start, if you
+        * have a really busy server, using N-1 where N is the number of
+        * cpu/cpu cores you have might be useful. A number greater than one
+        * can also be useful in case of bugs in ssld and because ssld needs
+        * two file descriptors per SSL connection.
         */
        ssld_count = 1;
 

diff --git a/doc/reference.conf b/doc/reference.conf
index 40b6d19c4d6c6f01498ff0e190bc61c7c6d08629..53297d1178aaca3c7581636703654a04fb8b8cce 100755 (executable)
--- a/doc/reference.conf
+++ b/doc/reference.conf
@@ -142,8 +142,11 @@ serverinfo {
        /* ssl_dh_params: DH parameters, generate with openssl dhparam -out dh.pem 1024 */
        ssl_dh_params = "etc/dh.pem";
 
-       /* ssld_count: number of ssld processes you want to start, if you have a really busy 
-        * server, using N-1 where N is the number of cpu/cpu cores you have might be useful
+       /* ssld_count: number of ssld processes you want to start, if you
+        * have a really busy server, using N-1 where N is the number of
+        * cpu/cpu cores you have might be useful. A number greater than one
+        * can also be useful in case of bugs in ssld and because ssld needs
+        * two file descriptors per SSL connection.
         */
        ssld_count = 1;