Manual:RunJobs.php/es

Detalles
runJobs.php file is a maintenance script to manually force the job queue to run. Under normal circumstances jobs in the queue are run as a function of user interaction with the wiki (ordinary apache requests). The default rate jobs are run is 1 to 1 and can be changed by adjusting in  file.

You may wish to use this script because your wiki's traffic is too slow to clear the queue, or there may be an exceptionally large number of jobs to clear. Be advised though that for many server configurations this can cause your wiki to become sluggish or even unresponsive until the script completes. You would be advised to first try 50 or 100 to get a feel for the script's speed before running it with no parameters (this script defaults to 10,000 jobs cleared each time it is run) or for more than a few hundred jobs.

Note also that if you accidentally ran a script that loaded the job queue with a large number of undesired or unneeded jobs it is also possible to completely clear the job queue by clearing the job table in your wiki database. Be certain there are no jobs in the queue you need as all jobs will be irretrievably deleted.

Uso
 php maintenance/runJobs.php

Uso avanzado
 php runJobs.php [--conf|--dbpass|--dbuser|--globals|--help|--maxjobs|--maxtime|--memory-limit|--nothrottle|--procs|--quiet|--server|--type|--wait|--wiki]

Ejemplo
 php maintenance/runJobs.php --maxjobs 5 --type refreshLinks

 /home/flowerwiki/public_html/w/maintenance$ php runJobs.php --maxjobs 5 --type refreshLinks

2010-10-29 13:50:38 refreshLinks Daisies t=501 good 2010-10-29 13:50:38 refreshLinks Magnolias t=501 good 2010-10-29 13:50:39 refreshLinks Heirloom_Roses t=500 good 2010-10-29 13:50:39 refreshLinks Carnations t=501 good 2010-10-29 13:50:40 refreshLinks Tulips t=563 good

Advertencia
"runJobs.php" may hang under certain circumstances if you have object caching enabled. If this happens, create another "LocalSettings.php" file without object caching enabled:

$wgMainCacheType = CACHE_DB;

Then run "runJobs.php" with the  parameter to specify the location of the new   file with caching disabled.

This is, however, not recommended, since some jobs will purge objects from the object cache, which won't get purged because caching is disabled. This will result in some updates not being reflected on the wiki. Ideally, you should find the cause of the problem, usually a missing PHP extension in the php.ini of the php being run from the command line.

Véase también

 * Job queue
 * table
 * Job queue redesign