Skip to content

fix(background_jobs_configuration) Add example #11497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 4, 2024
+11 −1
Merged

fix(background_jobs_configuration) Add example #11497

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion admin_manual/configuration_server/background_jobs_configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,17 @@ for this config, the background jobs which advertise themselves as not time-sens
will be delayed during the "working" hours and only run in the 4 hours after the given
time. This is e.g. used for activity expiration, suspicious login training, and update checks.

A value of 1 e.g. will only run these background jobs between 01:00am UTC and 05:00am UTC.
A value of 1 e.g. will only run these background jobs between 01:00am UTC and 05:00am UTC::

'maintenance_window_start' => 1,

If you don't care when these jobs run, you can set the value to ``100``, but beware that
resource intensive jobs may then run unnecessarily during high usage periods. This may lead to
slower performance and a lower quality user experience.

This setting may also be set directly via ``occ`` just like any other configuration parameter::

occ config:system:set maintenance_window_start --type=integer --value=1

Cron jobs
---------
Expand Down