System: System Scheduler
For normal usage, most administrators will not need to interact with this section. Functions here are for diagnostics, support, or advanced development.
The system scheduler allows IP.Board to perform various tasks required for smooth operation at different intervals. Tasks such as log pruning, topic subscription emails, and other timed events are executed through the scheduler.
The tasks can be viewed in Admin CP --> System --> System Scheduler.
The table lists the various tasks separated into tabs by the application that is relevant for them. You can edit or delete a task by clicking the appropriate option from the dropdown.
You will also see a icon that allows you to manually run a task.
This icon may be red, which means that the task was not able to run at it's last scheduled time, and so should be ran now.
There are also tools to add a new task, import and export tasks, but these are mainly only to be used by developers creating their own applications or modifications that require tasks - most users can ignore these tools.
If you see a task that is flagged with "LOCKED" - this means that the task has been locked after failing to run properly. You should check the logs (see below) to see what the problem was, and once fixed, remove the lock by selecting "Unlock Task" from the dropdown menu.
Using CRON jobs instead of the System Scheduler
On the system scheduler page, you will see an icon for each task. Clicking on this will show a cURL command which can be run in a CRON task.
To use a CRON job instead of the system scheduler, first set up a CRON job using the cURL command (you should schedule them to run at the same intervals the scheduler has set up) and then disable the task from the edit screen.
You should do this for each of your tasks.
You can view logs of tasks ran in Admin CP --> Logs --> Scheduler Logs.
Some tasks will not create a log if they are run often. You can turn logging on or off for any task in the settings for that task.