164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
|
for a repository:
> fossil test-backoffice-lease -R _REPOSITORY_
Running that command every few seconds should show what is going on with
backoffice processing in a particular repository.
There are also two settings that control backoffice behavior. The
"backoffice-nodelay" setting prevents the "next" process from taking a
lease and sleeping. If "backoffice-nodelay" is set, that causes all
backoffice processes to exit either immediately or after doing whatever
backoffice works needs to be done. If something is going wrong and
backoffice leases are causing delays in webpage processing, then setting
"backoffice-nodelay" to true can work around the problem until the bug
can be fixed. The "backoffice-logfile" setting is the name of a log
file onto which is appended a short message everything a backoffice
process actually starts to do the backoffice work. This log file can
be used to verify that backoffice really is running, if there is any
doubt. Most installations should leave "backoffice-nodelay" off and
|
|
>
>
>
>
>
|
>
|
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
for a repository:
> fossil test-backoffice-lease -R _REPOSITORY_
Running that command every few seconds should show what is going on with
backoffice processing in a particular repository.
There are also settings that control backoffice behavior. The
"backoffice-nodelay" setting prevents the "next" process from taking a
lease and sleeping. If "backoffice-nodelay" is set, that causes all
backoffice processes to exit either immediately or after doing whatever
backoffice works needs to be done. If something is going wrong and
backoffice leases are causing delays in webpage processing, then setting
"backoffice-nodelay" to true can work around the problem until the bug
can be fixed. The "backoffice-logfile" setting is the name of a log
file onto which is appended a short message everything a backoffice
process actually starts to do the backoffice work. This log file can
be used to verify that backoffice really is running, if there is any
doubt. The "backoffice-disable" setting prevents automatic backoffice
processing, if true. Use this to completely disable backoffice processing
that occurs automatically after each HTTP request. The "backoffice-disable"
setting does not affect the operation of the manual
"fossil backoffice" command.
Most installations should leave "backoffice-nodelay" and "backoffice-disable"
set to their default values of off and
leave "backoffice-logfile" unset or set to an empty string.
|