Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 23E684763FE for ; Fri, 4 Oct 2002 11:28:48 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id BF58147705C for ; Fri, 4 Oct 2002 11:22:26 -0400 (EDT) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1771439; Fri, 04 Oct 2002 08:20:43 -0700 From: "Josh Berkus" Subject: Re: Authenticating user To: adriantineo@softhome.net Cc: pgsql-php@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 04 Oct 2002 08:20:43 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/12 X-Sequence-Number: 1527 Adrian, > Yes, that's what I did in the end. Thank you. > I didn't want that solution at first because I wanted to separate the > error for bad credentials from the error for db server not running. I > managed to do that by "output buffering" the error message and > analysing the string. FYI, we're using pam_auth together with a remote NFS authentication server to validate the users of our latest intranet project. It works flawlessly. -Josh Berkus