Actions
Bug #66300
closedmemory_limit = -1 must not trigger System Status Notification
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2015-04-07
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
The CLI setting for memory limit in php.ini
memory_limit = -1
produces a warning email for me with the reports scheduler task executed via CLI on 6.2.11:
One or more problems were detected with your TYPO3 installation. Please check the status report for more information. Site: XYZ Issues: [ERR] PHP Memory Limit - -1
Updated by Markus Klein over 9 years ago
- Status changed from New to Needs Feedback
Is -1 a valid value at all?
I only know 0 for infinite.
Updated by Stephan Großberndt over 9 years ago
http://php.net/manual/en/ini.core.php#ini.sect.resource-limits
This sets the maximum amount of memory in bytes that a script is allowed to allocate. This helps prevent poorly written scripts for eating up all available memory on a server. Note that to have no memory limit, set this directive to -1.
Updated by Alexander Opitz over 9 years ago
Hi,
does something changed for this? I get this only as warning:
[WARN] Systemumgebungsüberprüfung - 2 Test(s) ### Unlimited memory limit for PHP: warning ### Low PHP script execution time: warning
Updated by Alexander Opitz about 9 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
next-patchlevel)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Actions