From d5c13223914913c8bc223e98fb21474f9c11b99b Mon Sep 17 00:00:00 2001 From: Felix Bartels Date: Tue, 11 Apr 2017 08:41:11 +0200 Subject: Correct link to "background_job_file" (#127) update link for current file structure --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f4a2e893a..77fc71766 100644 --- a/README.md +++ b/README.md @@ -258,7 +258,7 @@ System Cron: * Check the file permissions of the **cron.php** file and if **www-data** (or whatever your httpd user is called like) can read and execute that script * Check if you can execute the cron with **sudo -u www-data php -f nextcloud/cron.php** (replace www-data with your httpd user) * Check your **data/nextcloud.log** for errors -* Check if the cronjob is ever executed by placing an **error_log('updating');** in the [background job file](https://github.com/nextcloud/news/blob/master/cron/updater.php#L28). If the cronjob runs, there should be an updating log statement in your httpd log. +* Check if the cronjob is ever executed by placing an **error_log('updating');** in the [background job file](https://github.com/nextcloud/news/blob/master/lib/Cron/Updater.php#L28). If the cronjob runs, there should be an updating log statement in your httpd log. * If there is no **updating** statement in your logs check if your cronjob is executed by executing a different script * Check if the **oc_jobs** table has a **reserved_at** entry with a value other than 0. If it does for whatever reason, set it to 0. You can check this by executing: -- cgit v1.2.3