From owner-freebsd-database Thu Jan 29 20:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06066 for database-outgoing; Thu, 29 Jan 1998 20:19:50 -0800 (PST) (envelope-from owner-freebsd-database@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA06015 for ; Thu, 29 Jan 1998 20:19:22 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 10384 invoked by uid 1000); 30 Jan 1998 04:26:32 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 29 Jan 1998 20:26:32 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: The Hermit Hacker , freebsd-database@FreeBSD.ORG Subject: Re: your mail Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe database" I am redirecting to the database list, which is more appropriate. I think. On 29-Jan-98 The Hermit Hacker wrote: > On Thu, 29 Jan 1998, Simon Shapiro wrote: > >> I am on shaky ground here, so be kind to me: >> >> I am trying to get a very new PostgreSQL snapshot to work. >> One of the things it does is create a UNIX Socket in /tmp. >> It uses a template to create the ``filename'': >> >> #define UNIXSOCK_PATH(sun,port) \ >> (sprintf((sun).sun_path, "/tmp/.s.PGSQL.%d", (port)) + \ >> sizeof ((sun).sun_family)) >> >> This seems to work OK (I traced it in the RDBMS code), up to the bind >> syscall. The port is 5432, and the socket gets created as: >> >> srwx------ 1 pgsql bin 0 Jan 27 16:18 /tmp/.s.PGSQL.543 >> >> The bind(2) call is: > > > Just curious, but I'm running the snapshot on my 3.0-CURRENT > machine and I can run the full regression tests without a problem...what > sort of problem are you experiencing? Cannot connect. It looks like either the pg_hba.conf file is incorrect (including the one which works in 6.2.1), or that the sockets cannot be opened. While digging, I see that the filename representing the Unix socket is wrong (the last digit gets truncated). I need to try today's snapshot. Maybe the problem is gone. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313