-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
Documentation: backgroud jobs 15 min vs. 5 min #1587
Comments
Mind to use the "Edit on GitHub" button on [2] to suggest such a change? |
#1588 |
5mins is actually correct. |
@nickvergessen Is keeping 15 minutes a problem? Some even take longer times during the night to avoid their disks from spinning up. How critical is this setting? |
Well it depends on the size of your instance and the live-ness you want to feel. You should check the oc_jobs table regularly and see if it starts growing (then its run too few) |
So, if it's about your 1 user home instance sure, 15mins and save some energy. |
The background jobs configuration page [1] of my installation offers three options [german]:
"AJAX
Eine Aufgabe bei jedem Laden einer Seite ausführen
Webcron
cron.php ist als Webcron-Dienst registriert, der die cron.php alle 15 Minuten per HTTP aufruft.
Cron
Nutzen Sie den System-Cron-Service um cron.php alle 15 Minuten aufzurufen. Die cron.php muss durch den Systemnutzer "wwwrun" ausgeführt werden. "
Both cron options mention a 15 minute cycle.
The corresponding documentation [2] mentions in the examples always a 5 minute cycle.
(e.g. "To run a cron job on a *nix system, every 5 minutes, under the default Web server user (often, www-data or wwwrun), you must set up the following cron job to call the cron.php script:")
I suggest to change the documentation to 15 minutes (6 hits on that page).
[1] https:///index.php/settings/admin
[2] https://docs.nextcloud.com/server/16/admin_manual/configuration_server/background_jobs_configuration.html
The text was updated successfully, but these errors were encountered: