Improve php-fpm -t
还没有人认领这个 Issue。
- 主要语言
- C
- 星标
- 40.4k
- 派生
- 8.1k
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 96
描述
Description
if pool.conf contains:
php_admin_value[memory_limit] = 128MB
it does not overwrite the global php.ini,except memory_limit is not set in php.ini, than 128M will be used.
this is either coaccidently the php build in default
OR
an emergc fall back in php-fpm to as in "better try this than nothing"
Suggestion:
add checks to "php-fpm -t" to find:
a) wrong arguments
b) stupid configs which will cause php-fpm master to crash in an endless loop with "code 70"
c) "if you know something, say something"
Example:
if "process.max = 80" is lower than an start servers together ( or other sanity checks ) , than say something and don't lure the using user in a false hope of "it can work" , just to endless crash with "code 70" which tells you: i crash, but not why i crashed" which is VVVVVVEEEEEEERRRYYYY annoying btw.
PHP 8.4.18 (fpm-fcgi) (built: Feb 10 2026 17:48:03) (NTS gcc x86_64)
Copyright (c) The PHP Group
Built by Fedora Project
Zend Engine v4.4.18, Copyright (c) Zend Technologies
with Zend OPcache v8.4.18, Copyright (c), by Zend Technologies
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未指定源文件或测试。首先使用 php-fpm -t 重现所报告的 pool.conf 和 php.ini 行为,然后跟踪验证入口点和现有的错误报告机制。完成时应包括针对无效或不安全配置的已达成一致的检查、可采取行动的诊断信息,以及覆盖这些检查的测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- c, php
- 领域
- backend
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100