On Tue, Aug 07, 2012 at 18:46:08 -0700, Pete Stieber <pstie...@gmail.com> wrote:
Just to see if it is the cause of the problem. Once this is determined...
I told you what it almost certainly was yesterday. httpd uses private tmp space by default and can't see the system /tmp where postgres puts its connection file.
Two possible solutions are two connect to postgres over the loopback network or to have httpd not run with with a private /tmp space.
This was discuss on one of the lists before f17 went live. The postgres domain socket has been in /tmp for a long time and moving it (to say /run) will break things. If the tools / people that use postgres are limited a third option would be to configure postgres to put its domain sock in /run. However this is pretty fragile and I'd suggest using one of the other two solutions.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
