Wissensdatenbank

Overview:

Cron jobs schedule scripts to run at predefined times or intervals on the server. This interface allows you to configure the upcp, backup, and cpbackup scripts’ cron jobs on your server.

Configure a cron job

To configure a cron job, perform the following steps:

1. Enter the desired intervals for the cron job that you wish to configure. For more information, read the Cron job intervals section below.
2. Click Commit.

Cron job intervals

Set the following variables to configure each cron job:

• Minute — Enter the minute of each hour at which to run the cron job. For example, enter 15 to run the cron job at 15 minutes past the hour.
• Hour — Enter the hour of each day (in 24-hour format) at which to run the cron job. For example, enter 2100 to run the cron job at 9:00 PM local time.
• Day — Enter the day of the month on which to run the cron job. For example, enter 15 to run the cron job on the 15th of the month.
• Month — Enter the month of the year in which to run the cron job. For example, enter 7 to run the cron job in July.
• Weekday — Enter the day(s) of the week on which to run the cron job. For example, a value of 0 indicates Sunday, or a value of 6 indicates Saturday.

For example, to schedule a process to run every day at 9:15 PM (or 21:15 in 24-hour format), use the following settings:

The upcp command

The upcp script updates cPanel & WHM. By default, the upcp script runs at a random time between 9:00 PM and 6:00 AM local time.

The backup command

The backup script runs the backups that you configure in WHM’s Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration). By default, this script runs at 2:00 AM local time, because this is an off-peak time for most servers. If you have disabled backups in the Backup Configuration interface, the script immediately exits after it runs.

The cpbackup command

The cpbackup script runs legacy backups on your server. By default, this script runs at 1:00 AM local time, because this is an off-peak time for most servers. If you have disabled legacy backups, the script immediately exits after it runs.