xF2 Beta - CLI Job Runner | NulledTeam UnderGround | The Best Scripts Site In The World
  • Read Our Rules

    Dont forget read our rules Nulled Team UnderGround Rules

  • You may not say thanks or replied bad language in a thread - Your reply will be removed and warning! You must be like us "overview" in the resource. You will be access to download in FREE SECTION ONLY! DO NOT PREMIUM SECTION! Is only upgrade to up account.
  • Please support our site and click on the advertised
  • Complete Installation Service

    Review Our XenForo Complete Installation Service
  • Multiple Accounts

    Dont forget we not allowed Multiple Accounts, so all of your accounts as well as your IP will ban

Resource icon

xF2 Beta CLI Job Runner 1.0.0

No permission to download
Compatible XF Versions 2.x
This XenForo 2.0 addon disables the browser triggered job runner and implements a CLI triggered job runner for use with Unix cron.


This addon requires PHP 5.4 or higher and only works on XenForo 2.0.x


Install as per normal addon installation.

Note: once this addon is installed and activated, scheduled tasks will no longer run - so completing the remaining installation steps is critical to ensure your forum continues to function normally.

First, you should test that your job runner is functioning - execute the following command from your CLI:
You don't have permission to view the code content.
For example, if your forum root is /srv/www/xenforo/community, then the job runner command would be:

You don't have permission to view the code content.
Running this command will execute any outstanding jobs and then finish with a message about whether there are more jobs waiting to be executed or not. When executing this command from cron, it is recommended that you use the --quiet (or -q) flag to suppress output.

Once you are happy that the job runner functions, you will need to create your own cron task to run it on a schedule of your choosing.

It is highly recommended that you have your cron task run as the web server user to prevent potential permission problems.

For example, on Ubuntu with a web server user of www-data, install a cron task by running the following command:

You don't have permission to view the code content.
Edit the crontab file and add:

You don't have permission to view the code content.
Save the crontab.

This will execute the job runner every minute, checking for outstanding jobs to be run.

By default, the job runner will run for a maximum of 30 seconds, executing any outstanding jobs until there are no more runnable jobs in the queue.


You may adjust the maximum execution time of the job runner by specifying the --time=[TIME] option on the command line.

For example, to allow the job runner to execute for a maximum of 45 seconds:

You don't have permission to view the code content.
It is not recommended that you allow the job runner to run for longer than the period between cron triggers. For example, the above cron task example will execute the job runner every minute, so setting the maximum run time to more than 60 is generally a bad idea.

If you prefer to not run the cron task as frequently as once per minute, you can adjust the cron job as
required and if you do, you may also want to allow the job runner task to run for longer than the default 30 seconds to ensure that all outstanding work is completed.

For example, to run the cron task every 5 minutes, allowing the job runner to execute for a maximum of 4 minutes, use the following cron command:

You don't have permission to view the code content.
For further customisation of your job execution, you may also adjust the maximum time that each job is permitted to run.
This is configured via a XenForo config.php Option:

You don't have permission to view the code content.
The jobMaxRunTime option configures the amount of time in seconds that processing jobs will be allowed to run before they are suspended for further processing on another go-around, if possible. The default setting is optimised for the browser-triggered job runner and so to allow jobs to execute longer in a CLI environment, you may want to adjust this to a higher value.

You should not set jobMaxRunTime to anything higher than 30 seconds, or the time specified by the --time option. In general it is suggested that this setting be kept to a relatively small value to avoid the situation where a single very long job may prevent other jobs from executing in a timely manner. Some experimentation may be required to find the optimal value for your server load and forum size.
First release
Last update
0.00 star(s) 0 ratings

More resources from AnimeHaxor

Share this resource

Dear User!

We found that you are blocking the display of ads on our site.

It looks like you're using an ad blocker. That's okay. Who doesn't?

But without advertising-income, we can't keep making this site awesome.

Thank you for understanding!