Fossil SCM
Update www/loadmgmt.md to match the current behavior, per feedback in the forum.
Commit
53a065900f045ca6b08cc9df6a1e877d181bed1171976ed11444e17155fbc7f1
Parent
a66a14b033831ba…
1 file changed
+5
-2
+5
-2
| --- www/loadmgmt.md | ||
| +++ www/loadmgmt.md | ||
| @@ -25,15 +25,18 @@ | ||
| 25 | 25 | 1. An optional cache is available that remembers the 10 most recently |
| 26 | 26 | requested `/zip` or `/tarball` pages and returns the precomputed |
| 27 | 27 | answer if the same page is requested again. |
| 28 | 28 | |
| 29 | 29 | 2. Page requests can be configured to fail with a |
| 30 | - “[503 Server Overload][503]” HTTP error if an expensive request is | |
| 30 | + “[503 Server Overload][503]” HTTP error if any request is | |
| 31 | 31 | received while the host load average is too high. |
| 32 | 32 | |
| 33 | 33 | Both of these load-control mechanisms are turned off by default, but |
| 34 | -they are recommended for high-traffic sites. | |
| 34 | +they are recommended for high-traffic sites. Users with [admin | |
| 35 | +permissions](caps/index.md) are exempt from these restrictions, | |
| 36 | +provided they are logged in before the load gets too high (login is | |
| 37 | +disabled under high load). | |
| 35 | 38 | |
| 36 | 39 | The webpage cache is activated using the [`fossil cache init`](/help/cache) |
| 37 | 40 | command-line on the server. Add a `-R` option to |
| 38 | 41 | specify the specific repository for which to enable caching. If running |
| 39 | 42 | this command as root, be sure to “`chown`” the cache database to give |
| 40 | 43 |
| --- www/loadmgmt.md | |
| +++ www/loadmgmt.md | |
| @@ -25,15 +25,18 @@ | |
| 25 | 1. An optional cache is available that remembers the 10 most recently |
| 26 | requested `/zip` or `/tarball` pages and returns the precomputed |
| 27 | answer if the same page is requested again. |
| 28 | |
| 29 | 2. Page requests can be configured to fail with a |
| 30 | “[503 Server Overload][503]” HTTP error if an expensive request is |
| 31 | received while the host load average is too high. |
| 32 | |
| 33 | Both of these load-control mechanisms are turned off by default, but |
| 34 | they are recommended for high-traffic sites. |
| 35 | |
| 36 | The webpage cache is activated using the [`fossil cache init`](/help/cache) |
| 37 | command-line on the server. Add a `-R` option to |
| 38 | specify the specific repository for which to enable caching. If running |
| 39 | this command as root, be sure to “`chown`” the cache database to give |
| 40 |
| --- www/loadmgmt.md | |
| +++ www/loadmgmt.md | |
| @@ -25,15 +25,18 @@ | |
| 25 | 1. An optional cache is available that remembers the 10 most recently |
| 26 | requested `/zip` or `/tarball` pages and returns the precomputed |
| 27 | answer if the same page is requested again. |
| 28 | |
| 29 | 2. Page requests can be configured to fail with a |
| 30 | “[503 Server Overload][503]” HTTP error if any request is |
| 31 | received while the host load average is too high. |
| 32 | |
| 33 | Both of these load-control mechanisms are turned off by default, but |
| 34 | they are recommended for high-traffic sites. Users with [admin |
| 35 | permissions](caps/index.md) are exempt from these restrictions, |
| 36 | provided they are logged in before the load gets too high (login is |
| 37 | disabled under high load). |
| 38 | |
| 39 | The webpage cache is activated using the [`fossil cache init`](/help/cache) |
| 40 | command-line on the server. Add a `-R` option to |
| 41 | specify the specific repository for which to enable caching. If running |
| 42 | this command as root, be sure to “`chown`” the cache database to give |
| 43 |