Upstream's sample configuration (sapi/fpm/php-fpm.conf.in) suggests
using the "listen 127.0.0.1:9000" directive in your pools. This is
what most software expect of php-fpm, and using the 'unix socket'
approach breaks this assumption.

Compare those two google searches:

 * 32 000 results: php-fpm "listen 127.0.0.1:9000"
 * 4,760 results: php-fpm "listen /tmp/php-fpm.sock"
 * 1,630 results: php-fpm "listen /var/run/php5-fpm.sock"

Now I understand this is a Debian-specific change that was introduced
in 5.4.0~rc7-2, to respond to another bug report, #650204.

I think the reasoning behind the request is not sufficient to warrant
this change. It was mentionned this was "easier" to use, but I fail to
see why. Everywhere I can see, people are *not* using sockets to talk
to php-fpm, so I feel it breaks the POLA (Principle Of Least Astonishment).

The ubuntu issue mentions checking with upstream for the change, but
as far as I can see, upstream still suggests port 9000 in the sample
configuration.

Can we revert back to the upstream configuration please?