From d743d2b89279ac78dc083fcb03b383c265fac1fa Mon Sep 17 00:00:00 2001 From: Faraz Samapoor Date: Tue, 18 Jul 2023 16:12:06 +0330 Subject: [PATCH] Update background_jobs_configuration.rst Co-authored-by: Marcel Klehr Signed-off-by: Faraz Samapoor --- .../configuration_server/background_jobs_configuration.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/admin_manual/configuration_server/background_jobs_configuration.rst b/admin_manual/configuration_server/background_jobs_configuration.rst index 638b49776..2e8b450af 100644 --- a/admin_manual/configuration_server/background_jobs_configuration.rst +++ b/admin_manual/configuration_server/background_jobs_configuration.rst @@ -4,7 +4,7 @@ Background jobs A system like Nextcloud sometimes requires tasks to be done on a regular basis without the need for user interaction or hindering Nextcloud performance. For that purpose, as a system administrator, you can define background jobs (for -example, database clean-ups) which are executed without any need for the user +example, database clean-ups) which are executed without any need for user interaction. These jobs are typically referred to as *cron jobs*. Cron jobs are commands or @@ -69,7 +69,7 @@ access your server using the Internet. For example:: URL to call: http[s]:///nextcloud/cron.php .. warning:: Since WebCron is still executed via the web, the webserver in most cases limits the - resources on the execution. To avoid interrupting inside jobs only 1 job is executed + resources on the execution. To avoid interrupts inside jobs only 1 job is executed per call. When webcron is called once every 5 minutes this limits your instance to 288 background jobs per day, which is only suitable for very small instances. For bigger instances, it is recommended to use ``cron``.