Cron with Unix or Linux: Difference between revisions
m (Updated, and deleted (very) old information) |
|||
(9 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{ | {{Installing Moodle}} | ||
On Unix and Linux use the built in ''cron'' program which is standard on nearly all systems. You are required to add a command to the 'crontab' (the table that holds cron commands) for the web server user. | On Unix and Linux use the built in ''cron'' program which is standard on nearly all systems. You are required to add a command to the 'crontab' (the table that holds cron commands) for the web server user. | ||
Line 8: | Line 8: | ||
== Method 1: The command line (cli) cron == | == Method 1: The command line (cli) cron == | ||
If you have the PHP CLI version installed then this is the recommended method of invoking cron. The correct command | If you have a choice, this is normally the best way to run Moodle cron. | ||
PHP is also capable of running programs directly from the command line. Your system needs to be set up to do this; specifically you need the 'CLI' version of PHP to be installed. Most systems with PHP installed will have this by default. If you have the PHP CLI version installed then this is the recommended method of invoking cron. The correct command will be something like... | |||
<pre> | <pre> | ||
/usr/bin/php /path/to/moodle/admin/cli/cron.php | /usr/bin/php /path/to/moodle/admin/cli/cron.php | ||
Line 15: | Line 17: | ||
You can simply type this on the command line this to see if it works. If you are not sure about the path to PHP you can type "<code>which php</code>". | You can simply type this on the command line this to see if it works. If you are not sure about the path to PHP you can type "<code>which php</code>". | ||
'''Tip:''': If you have problems, see the [[PHP]] page. In particular, suspect an alternate php.ini for the CLI PHP command which may not have suitable settings. | '''Tip:''': If you have problems, see the [[PHP]] page. In particular, suspect an alternate php.ini for the CLI PHP command which may not have suitable settings. | ||
Line 29: | Line 29: | ||
</pre> | </pre> | ||
A command line (text based) browser is needed to run this | A command line (text based) browser is needed to run this on the server. Possibilities are as follows (OSX, for example, only ships with curl)... | ||
<pre> | <pre> | ||
/usr/bin/wget -q -O /dev/null/ http://url.of.your/moodle/admin/cron.php | /usr/bin/wget -q -O /dev/null/ http://url.of.your/moodle/admin/cron.php | ||
Line 44: | Line 44: | ||
==Using the crontab program on Unix/Linux== | ==Using the crontab program on Unix/Linux== | ||
Once you have selected (and tested!) an appropriate command to invoke the Moodle cron it must be added to the web users 'crontab' to schedule it to run regularly. Use the following command (as root) substituting the correct user in place of 'www-data' (e.g. 'apache' for Centos, 'www-data' for Debian/Ubuntu - Google will know!) | Once you have selected (and tested!) an appropriate command to invoke the Moodle cron it must be added to the web users 'crontab' to schedule it to run regularly. 'Crontab' is both a file containing the user's cron commands and is also the name of the (command line) program used to edit it. Use the following command (as root) substituting the correct user in place of 'www-data' (e.g. 'apache' for Centos, 'www-data' for Debian/Ubuntu - Google will know!) | ||
<pre> | <pre> | ||
# crontab -u www-data -e | # crontab -u www-data -e | ||
Line 50: | Line 50: | ||
This will bring up an editor window (the first time it may ask you which editor to use). Add the command onto the end of the file in this way (it may be empty or it may have some instructional comments): | This will bring up an editor window (the first time it may ask you which editor to use). Add the command onto the end of the file in this way (it may be empty or it may have some instructional comments): | ||
<pre> | <pre> | ||
*/ | */1 * * * * /usr/bin/php /path/to/moodle/admin/cli/cron.php >/dev/null | ||
</pre> | </pre> | ||
The first five entries specify the times, followed by the command, to run. This says to run the command every | The first five entries specify the times, followed by the command, to run. This says to run the command every minute which is normally ok. On a hosted system you may get complaints if you do not run it a lot less often (e.g. to run every two hours use '0 */2 * * *' for the first five entries). If you want to use the wget/curl version, the first five entries remain the same - just change the command part. | ||
== See also == | == See also == | ||
Line 58: | Line 58: | ||
* [http://linuxweblog.com/node/24 A basic crontab tutorial] | * [http://linuxweblog.com/node/24 A basic crontab tutorial] | ||
* [http://www.freebsd.org/cgi/man.cgi?query=crontab&apropos=0&sektion=5&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html Online version of the man page] | * [http://www.freebsd.org/cgi/man.cgi?query=crontab&apropos=0&sektion=5&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html Online version of the man page] | ||
* [http://www.easycron.com/predictor Predicting Cron job's run time] | |||
[[es:Cron con Unix o Linux]] |
Latest revision as of 08:40, 20 June 2016
On Unix and Linux use the built in cron program which is standard on nearly all systems. You are required to add a command to the 'crontab' (the table that holds cron commands) for the web server user.
There are two different methods that can be used to invoke the Moodle cron process:
NOTE: The commands shown need to be added to the crontab to function (described in a moment). However, you can - and should - run them on the command line to check they work first.
Method 1: The command line (cli) cron
If you have a choice, this is normally the best way to run Moodle cron.
PHP is also capable of running programs directly from the command line. Your system needs to be set up to do this; specifically you need the 'CLI' version of PHP to be installed. Most systems with PHP installed will have this by default. If you have the PHP CLI version installed then this is the recommended method of invoking cron. The correct command will be something like...
/usr/bin/php /path/to/moodle/admin/cli/cron.php
(substitute the correct path to moodle and for php as required)
You can simply type this on the command line this to see if it works. If you are not sure about the path to PHP you can type "which php
".
Tip:: If you have problems, see the PHP page. In particular, suspect an alternate php.ini for the CLI PHP command which may not have suitable settings.
Method 2: Web based cron
NOTE: In order to use the web based cron script you must first check Cron settings to make sure this method is permitted.
The idea is to call the following web page (you can try this from your browser):
http://url.of.your/moodle/admin/cron.php
A command line (text based) browser is needed to run this on the server. Possibilities are as follows (OSX, for example, only ships with curl)...
/usr/bin/wget -q -O /dev/null/ http://url.of.your/moodle/admin/cron.php
(no output is displayed - remove the -O /dev/null/ to test)
...OR...
/usr/bin/curl http://url.of.your/moodle/admin/cron.php -o /dev/null/ -silent
(no output is displayed - remove the -o /dev/null/ -silent to test)
Using the crontab program on Unix/Linux
Once you have selected (and tested!) an appropriate command to invoke the Moodle cron it must be added to the web users 'crontab' to schedule it to run regularly. 'Crontab' is both a file containing the user's cron commands and is also the name of the (command line) program used to edit it. Use the following command (as root) substituting the correct user in place of 'www-data' (e.g. 'apache' for Centos, 'www-data' for Debian/Ubuntu - Google will know!)
# crontab -u www-data -e
This will bring up an editor window (the first time it may ask you which editor to use). Add the command onto the end of the file in this way (it may be empty or it may have some instructional comments):
*/1 * * * * /usr/bin/php /path/to/moodle/admin/cli/cron.php >/dev/null
The first five entries specify the times, followed by the command, to run. This says to run the command every minute which is normally ok. On a hosted system you may get complaints if you do not run it a lot less often (e.g. to run every two hours use '0 */2 * * *' for the first five entries). If you want to use the wget/curl version, the first five entries remain the same - just change the command part.