Bug #20069: Misinterpretaion of php.ini settings when no limit is set - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #20069

closed

Misinterpretaion of php.ini settings when no limit is set

Added by Jo Schulze about 15 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Ernesto Baschny

Category:

Install Tool

Target version:

4.5.12

Start date:

2009-02-21

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.2

PHP Version:

5.2

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

After 1-2-3 installation the setup summary report
/install/index.php?TYPO3_INSTALL[type]=config

reports warnings about settings which in fact are perfctly ok:

memory_limit = -1 (no limit concerning memory) is reported as "Memory limit below 16MB"

max_execution_time = 0 (no limit concerning execution time) is reported as "Maximum execution time below 30 seconds"

(issue imported from #M10512)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Oliver Hader about 15 years ago

Hm... in general I don't think that setting no limits is a good idea. Scripts with memory leaks might run towards the moon until it's year 3000... ;-)

Actions

Copy link

Updated by Christian Kuhn about 15 years ago

I agree, its probably not a good idea to disable those limits.

But still, both values are documented as valid php.ini settings and I think the install tool should reflect this. Maybe a warning that these settings are unusual and might harm the system is a good idea.

http://de2.php.net/manual/en/info.configuration.php#ini.max-execution-time
http://de2.php.net/manual/en/ini.core.php#ini.memory-limit

Actions

Copy link