[pgpool-hackers: 1189] Re: Problem with pcp's UNIX domain socket

[Muhammad Usama]

Hi Ishii San

I don't think that PCP client side is required to recognize the
*pcp_socket_dir*, one because *pcp_socket_dir* only sets the directory
where the PCP server in pgpool-II would create the unix domain socket file.
And to connect to PCP server using the unix domain socket, pcp_* clients
needs to provide that path in hostname option of the command

For example, if pcp_socket_dir = '/tmp' the client can put this pcp_socket_dir
path in -h command line argument of pcp_* commands

$ bin/pcp_watchdog_info -h  /tmp/ -U postgres -v 0

Secondly, pcp_* frontend clients have no dependency on and visibility
of pgpool.conf file, so they have no idea about pcp_socket_dir value.


Thanks
Best regards
Muhammad Usama


On Tue, Dec 8, 2015 at 9:40 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> Usama,
>
> Does pcp recognize pcp_socket_dir? While searching libc/pcp.c, I could
> not find any reference to pcp_socket_dir.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
> _______________________________________________
> pgpool-hackers mailing list
> pgpool-hackers at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20151208/a79f1e25/attachment.html>