These instructions can also be used to edit an existing cron job you created in the panel, however for simplicity, it's recommended that if you created it in the panel, you continue to edit it from the panel.
The crontab files are where the lists of jobs and other instructions to the cron daemon are kept. Each user at DreamHost has their own individual crontab file that can be access by running the following command under your Shell user:
[server]$ crontab -e
Crontab files are simple text files that have a particular format. Each line of a crontab file follows a particular format as a series of fields, separated by spaces and/or tabs. Each field can have a single value or a series of values. A single cron job should take up exactly one line, but this can be a long line (more than 80 characters).
Things to look out for when editing/creating your crontab
Each line has five time/date fields, followed by a command, followed by a newline character ('\n'). A common problem is not including a newline, so hit 'Enter/Return' a time or three at the end of your command.
Another common problem is automatic word-wrap breaking up a long line into multiple lines, so make sure your text editor doesn't do this.
Blank lines and leading spaces and tabs are ignored. Lines whose first non-space character is a hash-sign (#) are ignored as they are considered comments. Note that comments are not allowed on the same line as cron commands, since they are interpreted as being part of the command. Similarly, comments are not allowed on the same line as environment variable settings (like MAILTO).
What if I already created a cron job in the panel under my Shell user?
There are two ways to create custom cron jobs.
- Editing the existing crontab on the server
- Using a custom crontab file
If you've edited the existing crontab
If you have already created a cron job in your panel, you can view it by running crontab -e under your Shell user. If you edit the file to add another cron job below the existing panel one, the panel cron job will continue to function normally in addition to your new edited code.
Any adjustments in the panel will not affect your custom code.
If you switched the server's crontab with your custom crontab
You can also use a custom crontab that you created. If you do this, the server's crontab is overwritten. You can replace the server's crontab by running the following:
[server]$ crontab /home/username/mycrontab
However, if you then add or edit a cron job in the panel, your custom crontab will be overwritten. So you need to either use the server's crontab, or your custom crontab.
Manually creating a custom cron job
The instructions below explain how to add a custom cron job under your Shell user. These instructions assume you have NOT added a cron job in the panel yet, so the crontab file is blank.
- Log into your server via SSH using the Shell user you wish to create the cron job under.
- Once logged in, run the following command to open your crontab file.
[server]$ crontab -e no crontab for example_username - using an empty one Select an editor. To change later, run 'select-editor'. 1. /bin/ed 2. /bin/elvis-tiny 3. /bin/nano <---- easiest 4. /usr/bin/emacs24 5. /usr/bin/jed 6. /usr/bin/jmacs 7. /usr/bin/joe 8. /usr/bin/jpico 9. /usr/bin/jstar 10. /usr/bin/mcedit 11. /usr/bin/rjoe 12. /usr/bin/vim.basic 13. /usr/bin/vim.tiny Choose 1-13 : 3
- You are then asked to choose an editor to view this file. #3 uses the program 'nano' which is the easiest option. View the 'Creating and editing a file via SSH' article for instructions on how to use nano.
- You are presented with this new crontab file:
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command
- At the bottom, add the code for your cron job. This example runs a file named mail.php under the username of 'example_username'. This should be the same username you're currently logged in under. This example runs the cron job at 8:13 pm.
# Custom cron job MAILTO="firstname.lastname@example.org" 13 20 * * * php /home/example_username/mail.php
There are two parts to the command. The first part must specify the path to the program you'd like to use to run the cron job. For example let's say you have a PHP file named script.php in your domains directory:
To run this command you'd enter the path to your chosen version of PHP followed by a space, followed by the path to the file:
- /usr/local/php71/bin/php /home/username/example.com/script.php
You could also use the default version by using 'php' instead of the full path.
- Save the file. You should see the following response:
crontab: installing new crontab
That's it. The cron job should now run every day at 8:13pm.
Please note that if you choose to replace the server's crontab, all cron jobs created in the panel for this specific username will no longer function since they would have been overwritten on the server.
Additionally, if you update any cron jobs under this user in the panel, it will overwrite your custom crontab. The crontab will be replaced in its original form as created in the panel.
Replace your existing crontab with your custom crontab file
[server]$ crontab /home/username/filename
Edit your server's crontab
[server]$ crontab -e
View your crontab
[server]$ crontab -l
Remove your crontab
[server]$ crontab -r
Explanation of the Date/Time fields
The first five fields of the line are the date and time field which specify how frequently and when to execute a command. When adding the cron job in the DreamHost panel, the Date/Time is added for you automatically based on your 'When to run' setting.
|Field no.||Description||Permitted values|
|3||day of the month||1-31|
|5||day of the week||0-7|
Note: For day of the week, both 0 and 7 are considered Sunday. The time is based on that of the server running cron.
Another (graphical) way of looking at these fields.
# * * * * * command to execute # │ │ │ │ │ # │ │ │ │ │ # │ │ │ │ └───── day of week (0 - 6) (0 to 6 are Sunday to Saturday, or use names; 7 is Sunday, the same as 0) # │ │ │ └────────── month (1 - 12) # │ │ └─────────────── day of month (1 - 31) # │ └──────────────────── hour (0 - 23) # └───────────────────────── min (0 - 59)
There are several ways of specifying multiple values in these fields:
- The comma (',') operator specifies a list of values.
- The dash ('-') operator specifies a range of values.
- This is equivalent to "1,2,3,4,5,6".
- The asterisk ('*') operator (frequently known as a wildcard) specifies all possible values for a field. For example, an asterisk in the hour (second) field would be equivalent to 'every hour'.
- The slash ('/') operator can be used in conjunction with an asterisk to skip a given number of values. Example:
- This means to skip to every third value. So "*/3" in the hour field is equivalent to "0,3,6,9,12,15,18,21"; "*" specifies 'every hour' but the "/3" means that only the first, fourth, seventh, etc. values given by "*" are used.
You can also use one of these special strings in place of the time/date fields.
||Run once a year at midnight on January 1||
||@yearly php /home/example_username/mail.php|
||Run once a month at midnight on the first day of the month||
||@monthly php /home/example_username/mail.php|
||Run once a week at midnight on Sunday morning||
||@weekly php /home/example_username/mail.php|
||Run once a day at midnight||
||@daily php /home/example_username/mail.php|
||Run once an hour at the beginning of the hour||
||@hourly php /home/example_username/mail.php|
||Run at startup (of the cron daemon)||
||@reboot php /home/example_username/mail.php|
Review the following Wikipedia article for further information:
The output of the cron job is determined by what is sent to the terminal as a result of the commands/script that are executed. By default, all output is emailed to the location specified in the MAILTO variable (see the MAILTO variable requirement section for more information). As noted above, if your cron job command doesn't create any output on the command line then no email is sent.
You can provide special instructions for the standard out (STDOUT) and standard error (STDERR) output by using the ">" operator. When you use ">" without a number before it, it defaults to "1>". This is the standard (non-error) output.
When you use "2>" you are specifying what to do with the error output. So, for example, ">my_file.txt" would redirect standard output to a file called "my_file.txt", and "2>my_errors.txt" would redirect the errors to a file called "my_errors.txt".
By default, files created on DreamHost's servers have a permissions level of 644. If you choose to execute a script via cron, you may need to set the permissions for the file to 744 using chmod in order to allow it to execute properly.
Examples of custom cron scripts
The following examples show what you could add to to a new file in order to create a cron job.
Example 1: This runs a command at 4:10 PM PST/PDT, and emails you the regular and error output to the destination specified by MAILTO.
10 16 * * * perl /home/username/bin/yourscript.pl
Example 2: This runs a command at 2:00 AM PST/PDT on Saturday, and the only output is errors.
0 2 * * 6 sh /home/username/weekly/weekly-pruning.sh > /dev/null
Example 3: This runs at midnight on New Years Day (January 1st), and there is no output.
0 0 1 1 0 python /home/username/happy.new.years.py >/dev/null 2>&1
2>&1 is a special redirect that sends the standard error (“2>”) output to the same place as the standard out (“>” or “1>”) output.
Example 4: This runs a PHP script called cron.php at the top of every hour.
0 * * * * php /home/username/cron.php
Example 5: This runs a local script (i.e. hosted at DreamHost) every 15 minutes.
*15 * * * * /usr/local/php71/bin/php /home/example_username/myscript.php
Example 6: This runs an external script (i.e. hosted elsewhere) every 30 minutes using curl.
*30 * * * * /usr/bin/curl -s http://example.com/send.php &> /dev/null
&>/dev/null is an abbreviation for 1> /dev/null 2> &1. It redirects both file descriptor 2 (STDERR) and descriptor 1 (STDOUT) to /dev/null.
View http://unix.stackexchange.com/a/70971 for more information.
Example 7: This runs a local script (i.e. hosted at DreamHost) every 10 minutes.
*/10 * * * * /usr/local/php71/bin/php /home/example_username/myscript.php
Example 8: This uses wget to download a file to a directory named /cronfolder.
*/10 * * * */usr/bin/wget -P /home/username/cronfolder/ https://example.com/index.html
Dedicated server editing
If you are logged in as a Dedicated server admin user, you can edit the crontab file directly. It is stored here:
You’ll need to use
sudo on your Dedicated server (or start an interactive session as the root user with
sudo -i) to access that file.
If you require sudo/admin access, you must upgrade to a Dedicated server.
Example (opening the file with the 'vi' text editor):
[server]$ sudo vi /var/spool/cron/crontabs/youruser