[php-maint] Bug#731055: Bug#731055: Bug#731055: php5-fpm: Extend the package sockets to multiply pools

Vitalii duke at ejoom.com
Thu Dec 12 11:48:50 UTC 2013

I do don't know any dependency from php5-fpm socket. Any web related 
packages work with 'www-data' user.
Apache works with php5-module, or if for cgi mode it should be 
configured manually.
Nginx and any other proxies don't rely on any php configs by default.
Any user who works with default config will not feel any changes.
Packages usually rely on user and user group not pool socket.
After managing of /etc/init.d/php5-fpm to proper on restart service and 
updating will break setups the same. So It will cause no more BC than 
updating nginx or php with changed configs in new version that asks 
update current config.
At last it will break no more than 1 pool setup.

And It really will be enough to add empty directory /var/run/php5-fpm, 
and at desire, another example pool like /etc/php5/fpm/pool.d/user.conf
with new socket path that will cause no BC impact.


On 12/12/2013 12:43 PM, Ondřej Surý wrote:
> The /etc/php5/fpm/pool.d was there from a very start, and we didn't
> release Debian squeeze with php5-fpm anyway, so this is really something
OK, may be, at that time I have been using Ubuntu packages.
> you should fix in your management scripts. The default is ok for the
> majority of the people and it's very hard to change the default socket.
> Do you realize that that would break all existing setups?
> O.
> P.S.: I would also recommend you to not use the 'demand' verb, you might
> be seen as a rude person.
OK. There It meant strong asking.
> On Thu, Dec 12, 2013, at 11:37, Vitalii wrote:
>> Creating of pools also local policy, and It can be managed at one file
>> as it was at php5-fpm ver. 5.3 (file name was smth like
>> /etc/php5/fpm/pool.ini).
>> But at ver. 5.4 It was moved to separate directory /etc/php5/fpm/pool.d,
>> but sockets wasn't.
>> I demand fix it and move sockets to separate directory too.
>> On 12/12/2013 12:26 PM, Ondřej Surý wrote:
>>> I think this is a local policy issue and not the general packaging
>>> problem, and you would be better using some management software (puppet,
>>> ansible, etc...) to fix your local problem.
>>> O.
>>> On Fri, Dec 6, 2013, at 21:38, Vitalii wrote:
>>>> This was the reason of creating the issue. As I've wrote: '... and all
>>>> that it will touch.' that include adding of creating this directory to
>>>> start service script.
>>>> As I see there is 3 places: change path in www pool config to proper.
>>>> Add validation to /etc/init.d/php5-fpm script for existence of directory
>>>> '/var/run/php5-fpm' if not then create it. Maybe somewhere else.
>>>> Ccing BTS so it is kept archived. On Fri, Dec 6, 2013, at 12:32, Vitalii
>>>> wrote:
>>>>>>         So my proposition to move www pool socket to
>>>>>> '/var/run/php5-fpm/www.sock' and all that it will touch. It'll enough.
>>>>> It won't help alone. If you add directories in (/var)/run you need to
>>>>> recreate them on the system start since /run is a tmpfs that get's
>>>>> recreated on system startup.
>>>>> So just changing the directory doesn't really solve anything.
>>>>> Ondrej
>>>> _______________________________________________
>>>> pkg-php-maint mailing list
>>>> pkg-php-maint at lists.alioth.debian.org
>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint

More information about the pkg-php-maint mailing list