[Kolab-devel] gunnar: server/php Makefile, 1.17, 1.18 kolab.patch, 1.13, 1.14 KOLAB_php-5.2.6_Annotations.patch, 1.1, NONE KOLAB_php-5.2.6_myrights.patch, 1.1, NONE

[Thomas Arendsen Hein]

Hi Gunnar!

* cvs at kolab.org <cvs at kolab.org> [20090209 11:08]:
> Author: gunnar
> 
> Log Message:
> Update to current 5.2.8 patches.
> 
> ===================================================================
> RCS file: /kolabrepository/server/php/kolab.patch,v
> retrieving revision 1.13
> retrieving revision 1.14
>...
> +--- php.ini.orig	2009-02-09 09:26:40.000000000 +0000
> ++++ php.ini	2009-02-09 09:27:01.000000000 +0000
> +@@ -13,8 +13,8 @@
> + log_errors         = on     ; Errors will be logged
> + max_execution_time = 60     ; Maximum execution time of each script, in seconds
> + max_input_time     = 60     ; Maximum amount of time each script may spend parsing request data
> +-memory_limit       = 8M     ; Maximum amount of memory a script may consume
> +-post_max_size      = 8M     ; Maximum amount of POST data accepted
> ++memory_limit       = 128M   ; Maximum amount of memory a script may consume
> ++post_max_size      = 128M   ; Maximum amount of POST data accepted
> + 
> + ;   Include Paths
> + include_path          = ".:@l_prefix@/lib/php"

Increasing the limits from 8M to 128M looks like an accidental slip
when not mentioned in the commit message.

Is this intentional? If yes, why?

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner