This answers a question I was asking on my first installation. The following (important) correction to the comment in authpgsqlrc:
##NAME: LOCATION:0 # # The server hostname, port, userid, and password used to log in. # # To connect to a socket, delete PGSQL_HOST, and put the socket filename # into PGSQL_PORT PGSQL_HOST pgsql.example.com PGSQL_PORT 5400 PGSQL_USERNAME admin PGSQL_PASSWORD admin Is incorrect. If postgres is using /tmp/.s.PGSQL.5432 as its socket, and you follow the above directions and set PGSQL_PORT /tmp/.s.PGSQL.5432 then an syscall trace on an authdaemon process shows that it fails with an ENOENT trying to open /tmp/.s.PGSQL.0 (iirc - I discovered this at 3:00 am). What works is setting PGSQL_PORT to 5432. It seems that the PORT is taken as a string to append to "/tmp/.s.PGSQL." when the postgres client lib tries to connect to the unix domain socket. Sam, can you correct this in the next release? -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
