Fossil SCM
[Grammar] backoffice.md changes.
Commit
e2d9ce6d5addf2fda9086deb519883dab7f04aea896f309eaceedbd51c7eb758
Parent
c6a6cd11bd6123b…
1 file changed
+3
-3
+3
-3
| --- www/backoffice.md | ||
| +++ www/backoffice.md | ||
| @@ -115,14 +115,14 @@ | ||
| 115 | 115 | launching the backoffice for all of them. There are additional useful |
| 116 | 116 | command-line options. See the "[fossil backoffice](/help?cmd=backoffice)" |
| 117 | 117 | documentation for details. |
| 118 | 118 | |
| 119 | 119 | The backoffice processes run manually using the "fossil backoffice" |
| 120 | -command do not normally use a lease. That means that you run the | |
| 120 | +command do not normally use a lease. That means that if you run the | |
| 121 | 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | -you might have one backoffice running due command and another due | |
| 123 | +you might have one backoffice running due to a command and another due | |
| 124 | 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 | 125 | only downside is that it uses extra CPU time. |
| 126 | 126 | |
| 127 | 127 | How Backoffice Is Implemented |
| 128 | 128 | ----------------------------- |
| @@ -210,11 +210,11 @@ | ||
| 210 | 210 | backoffice processes to exit either immediately or after doing whatever |
| 211 | 211 | backoffice works needs to be done. If something is going wrong and |
| 212 | 212 | backoffice leases are causing delays in webpage processing, then setting |
| 213 | 213 | "backoffice-nodelay" to true can work around the problem until the bug |
| 214 | 214 | can be fixed. The "backoffice-logfile" setting is the name of a log |
| 215 | -file onto which is appended a short message everything a backoffice | |
| 215 | +file onto which is appended a short message every time a backoffice | |
| 216 | 216 | process actually starts to do the backoffice work. This log file can |
| 217 | 217 | be used to verify that backoffice really is running, if there is any |
| 218 | 218 | doubt. The "backoffice-disable" setting prevents automatic backoffice |
| 219 | 219 | processing, if true. Use this to completely disable backoffice processing |
| 220 | 220 | that occurs automatically after each HTTP request. The "backoffice-disable" |
| 221 | 221 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -115,14 +115,14 @@ | |
| 115 | launching the backoffice for all of them. There are additional useful |
| 116 | command-line options. See the "[fossil backoffice](/help?cmd=backoffice)" |
| 117 | documentation for details. |
| 118 | |
| 119 | The backoffice processes run manually using the "fossil backoffice" |
| 120 | command do not normally use a lease. That means that you run the |
| 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | you might have one backoffice running due command and another due |
| 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 | only downside is that it uses extra CPU time. |
| 126 | |
| 127 | How Backoffice Is Implemented |
| 128 | ----------------------------- |
| @@ -210,11 +210,11 @@ | |
| 210 | backoffice processes to exit either immediately or after doing whatever |
| 211 | backoffice works needs to be done. If something is going wrong and |
| 212 | backoffice leases are causing delays in webpage processing, then setting |
| 213 | "backoffice-nodelay" to true can work around the problem until the bug |
| 214 | can be fixed. The "backoffice-logfile" setting is the name of a log |
| 215 | file onto which is appended a short message everything a backoffice |
| 216 | process actually starts to do the backoffice work. This log file can |
| 217 | be used to verify that backoffice really is running, if there is any |
| 218 | doubt. The "backoffice-disable" setting prevents automatic backoffice |
| 219 | processing, if true. Use this to completely disable backoffice processing |
| 220 | that occurs automatically after each HTTP request. The "backoffice-disable" |
| 221 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -115,14 +115,14 @@ | |
| 115 | launching the backoffice for all of them. There are additional useful |
| 116 | command-line options. See the "[fossil backoffice](/help?cmd=backoffice)" |
| 117 | documentation for details. |
| 118 | |
| 119 | The backoffice processes run manually using the "fossil backoffice" |
| 120 | command do not normally use a lease. That means that if you run the |
| 121 | "fossil backoffice" command with --poll and you forget to disable |
| 122 | automatic backoffice by setting the "backoffice-disable" flag, then |
| 123 | you might have one backoffice running due to a command and another due |
| 124 | to a webpage access, both at the same time. This is harmless. The |
| 125 | only downside is that it uses extra CPU time. |
| 126 | |
| 127 | How Backoffice Is Implemented |
| 128 | ----------------------------- |
| @@ -210,11 +210,11 @@ | |
| 210 | backoffice processes to exit either immediately or after doing whatever |
| 211 | backoffice works needs to be done. If something is going wrong and |
| 212 | backoffice leases are causing delays in webpage processing, then setting |
| 213 | "backoffice-nodelay" to true can work around the problem until the bug |
| 214 | can be fixed. The "backoffice-logfile" setting is the name of a log |
| 215 | file onto which is appended a short message every time a backoffice |
| 216 | process actually starts to do the backoffice work. This log file can |
| 217 | be used to verify that backoffice really is running, if there is any |
| 218 | doubt. The "backoffice-disable" setting prevents automatic backoffice |
| 219 | processing, if true. Use this to completely disable backoffice processing |
| 220 | that occurs automatically after each HTTP request. The "backoffice-disable" |
| 221 |