go to bug id or search bugs for
I'm wondering why an error is raised when no default pool configuration file is present. For instance, for Debian, the package maintainer configures a default pool configuration file set with the www-data user. This fulfills default installation requirements for Debian, but in some cases, we would expect no default pool configuration file.
For instance, we're providing a control panel which allows to manage shared hosting environments . Mutliple PHP versions are provided through the panel (through PHP-FPM).
First of all, it should be noted that for security reasons, we never run PHP through the www-data user. PHP is run through dedicated unix users (one for each customer). So here, we don't need to have a default pool configuration set with www-data user, which will never be used. Thefore, on installation, this default file is removed by our backend.
To resume, when rebooting or when restarting the PHP-FPM instance, there should be no error when no pool file configuration is available. Instead, the daemon should not start (silently).
Add a Patch
Add a Pull Request
We would break expectations (and probably deploys) if we changed something that used to emit an error, to fail silently ... we cannot reasonably do this.