PgSQL builds its socket filename based on the port number for consistency (xfs from XFree86 does the same thing)... I believe that you can also omit the port entirely, and it will use its built-in defaults to find the appropriate socket.
On Wed, 2002-07-03 at 10:03, Peter C. Norton wrote: ... > 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. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek No, I will not fix your computer. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
