[horde] Horde 4.0.2 exhauses memory

[Jan Schneider]

Zitat von Patrick Domack <patrickdk at patrickdk.com>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Patrick Domack <patrickdk at patrickdk.com>:
>>
>>> Quoting Jan Schneider <jan at horde.org>:
>>>
>>>> Zitat von Patrick Domack <patrickdk at patrickdk.com>:
>>>>
>>>>> Quoting Reindl Harald <h.reindl at thelounge.net>:
>>>>>
>>>>>> And that is why i hate pear and want to use my rmps built from  
>>>>>> tarballs as all
>>>>>> the years before and SURE nobody needs to make this tarballs by  
>>>>>> hand, this
>>>>>> could be done automatic on the horde-servers and instead  
>>>>>> hundrets auf small
>>>>>> packages in the same structure as below
>>>>>>
>>>>>> -rw-r----- 1 builduser builduser 3,3K 2010-10-31 11:12 horde-dimp.spec
>>>>>> -rw-r----- 1 builduser builduser 7,4K 2010-10-31 11:12 horde-imp.spec
>>>>>> -rw-r----- 1 builduser builduser 5,5K 2010-09-29 14:46 horde-ingo.spec
>>>>>> -rw-r----- 1 builduser builduser 4,1K 2010-09-29 14:46  
>>>>>> horde-kronolith.spec
>>>>>> -rw-r----- 1 builduser builduser 3,2K 2010-09-07 23:41 horde-mimp.spec
>>>>>> -rw-r----- 1 builduser builduser 3,3K 2010-09-29 14:45 horde-nag.spec
>>>>>> -rw-r----- 1 builduser builduser  16K 2010-11-27 13:37 horde.spec
>>>>>> -rw-r----- 1 builduser builduser 6,4K 2010-09-29 14:46 horde-turba.spec
>>>>>> -rw-r----- 1 builduser builduser 3,3K 2010-09-07 23:41 horde-whups.spec
>>>>>>
>>>>>> WHAT SPEAKS AGAINST PEAR:
>>>>>> * rpm does not mix config/app-files
>>>>>> * rpm will install clean .rpmnew-files while update
>>>>>> * rpm can be tested on one machine and deplyoed in a defined version
>>>>>> * rpm have clean way for downgrades
>>>>>> * PEAR is packing all in one folder
>>>>>> * PEAR-Packages including configs can not be deployed
>>>>>> * PEAR-Packages have no defined version over a defined timeline
>>>>>>
>>>>>
>>>>> Well, bugs are bugs.
>>>>>
>>>>> But the overwriting of the config files is extreemly annoying.
>>>>>
>>>>> On each update, it wipes out my imp backend and mime_drivers configs.
>>>>
>>>> Because you don't read the documentation.
>>>>
>>>
>>> * IMPORTANT: Local overrides MUST be placed in backends.local.php, or
>>> * backends-servername.php if the 'vhosts' setting has been enabled  
>>> in Horde's
>>> * configuration.
>>>
>>> I took the if to mean the whole line, just just the name of the file.
>>
>> How about:
>
>  * IMPORTANT: Do Not Edit This File
>  * Local overrides MUST be placed in backends.local.php.
>  * If the 'vhosts' setting has been enabled in Horde's configuration,
>  * you can use backends-servername.php.

Thanks, we use this more explicit warning now.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/