cronjob.ini [CacheCleanupSettings]
The block [CacheCleanupSettings] of settings/cronjob.ini, with 3 setting(s).
Never edit settings/cronjob.ini itself: an update replaces it. Put the settings you change in an override, which wins over the shipped file:
settings/override/cronjob.ini.append.phpfor every siteaccess,settings/siteaccess/<siteaccess>/cronjob.ini.append.phpfor one siteaccess,extension/<extension>/settings/cronjob.ini.append.phpin an extension (read when the extension is active).
MaxAge
Seconds after which a file is removed whatever its expiry. A cold entry that
was still valid costs one regeneration. 0 removes only expired files.
Default: 172800.
# settings/override/cronjob.ini.append.php
[CacheCleanupSettings]
MaxAge=172800
*/ ?>IterationSleep
Microseconds to sleep after every 1000 files, to go easy on the disk. 0 = none.
Default: 0.
# settings/override/cronjob.ini.append.php
[CacheCleanupSettings]
IterationSleep=0
*/ ?>RenameAfterClear
After a global clear of a cache, move its whole directory aside in one rename
and delete it from there, instead of looking at every file. Entries stored
between the clear and the run are lost and generated again. disabled removes
file by file. A clear in the administration interface or with
bin/php/ezcache.php already moves the directory aside itself (site.ini
[FileSettings] RenameExpiredCaches) and records that here, so this run does
not move it a second time.
Default: enabled.
# settings/override/cronjob.ini.append.php
[CacheCleanupSettings]
RenameAfterClear=enabled
*/ ?>Related
Generated by ./console exp:help:examples from settings/cronjob.ini. Do not edit this page: change the source and generate again (how). Free documentation: GFDL 1.3 or later.