> You can do that in a more stylish and safer manner by using the
> unix_socket_permissions and unix_socket_group options.
Moving the socket file is also necessary for running in
a chrooted environment. And I'm not sure whether it's relevant,
but the 7.0 method of computing the socket file name (based
only on the port number) doesn't work for multiple instances
listening on the same port on different IP addresses.
