[horde] General question to "horde-autoloader-cache-prune"

Michael M Slusarz slusarz at horde.org
Tue May 20 19:52:31 UTC 2014

Quoting Arjen de Korte <arjen+horde at de-korte.org>:

> Citeren Patrick De Zordo <patrick at spamreducer.eu>:
>> Am 20.05.2014 10:17, schrieb Arjen de Korte:
>>> Citeren Jan Schneider <jan at horde.org>:
>>>> Zitat von Patrick De Zordo <patrick at spamreducer.eu>:
>>>>> Am 20.05.2014 09:19, schrieb Michael M Slusarz:
>>>>>> Absent any strange issues... never.
>>>>> OK thanks, just seeing on every "horde-alarms" cronjob "Cannot  
>>>>> write Autoloader cache to backend." in logs..
>>>>> Is this normal? Just ignore this message?
>>>> Run the script with the web server user.
>>> If you're using APC, it is probably the same problem as mentioned in
>>> http://osdir.com/ml/horde/2014-05/msg00005.html
>> Not using it, just "filesystem" caching..
> If you have APC installed, you really should set 'apc.enable_cli=1'  
> to prevent the above messages, regardless of the  
> $conf[cache][driver] setting.

For the autoloader cache, the $conf settings are irrelevant ...  
autoloader setup is required to bootstrap Horde, so we don't have  
access to $conf at that time.


Michael Slusarz [slusarz at horde.org]

More information about the horde mailing list