Forums / Setup & design / what does the subtreeexpirycleanup.php file do, anyway?
Massimiliano Bariola
Wednesday 14 June 2006 9:08:32 am
Hi,
I never needed to activate the cronjobs until now. So I gave it a few runs from CLI to see if all was ok before trying to cron them.
I ran it with
php runcronjobs.php -s flc_test_user --logfiles -d --sql
I was unable to understand _where_ those logfiles are produced, but it seems that the subtreeexpirycleanup.php script is taking AGES to execute - I am talking about 1.5 hours. Site has about 30000 content objects and makes extensive use of cache-blocks. but as far as I know, cache-blocks are automatically invalidated and regenerated on demand.
So my question is .... what's the subtreeexpirycleanup.php file used for? So far, my site has worked well without it, but I am beginning to think I am missing something here. can I safely omit it? and if so, _when should I be using it instead?
Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced? (I have a very big doubt as to which script is responsible for the "publish on approval" too .... is that the workflow one? or is also the notification one involved?)
thank you :-)
Max
Svitlana Shatokhina
Friday 27 October 2006 7:47:08 am
The "runcronjobs.php" script doesn't modify any ".log" files by default (log files are located in the "var/log" directory). If you need this, run the script using both "-d" and "--logfiles" parameters:
php runcronjobs.php -d -s your_siteaccess --logfiles
Best regards,Sveta
P.S. Sorry, I didn't observe that you already use both parameters..
Wednesday 22 November 2006 2:27:23 am
>...what's the subtreeexpirycleanup.php file used for?
If you are using the "cache-block" template function with the "subtree_expiry" parameter to cache the contents of a template block, this cache block will only expire if an object is published below the given subtree (instead of the entire content node tree). The "DelayedCacheBlockCleanup" setting located in the "[TemplateSettings]" section of the "site.ini" configuration file controls whether expired cache blocks with the "subtree_expiry" parameter will be removed immediately or not. If this setting is enabled, the expired cache blocks must be removed manually or using the "subtreeexpirycleanup.php" cron job script.
>Anyone from eZ can help in explaining what the single scripts do and where the cronjob logs are produced?
The cron job scripts will be documented soon.
P.S. http://ez.no/doc/ez_publish/technical_manual/3_8/features/cronjobs