pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dick Davies <rasputnik@hellooperator.net>
To: Kavan, Dan (IMS) <KavanD@imsweb.com>
Cc: PostgreSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: PAM ldap
Date: Tue, 18 Jan 2005 21:23:02 +0000
Message-ID: <20050118212302.GM26970@lb.tenfour> (raw)
In-Reply-To: <782D2A81EC812642B857B03B506E0B4432637F@granite.omni.imsweb.com>
References: <782D2A81EC812642B857B03B506E0B4432637F@granite.omni.imsweb.com>

* Kavan, Dan (IMS) <KavanD@imsweb.com> [0156 16:56]:
> Thanks for the reply,
> 
> I did compile --with-pam.   Although, the $PATH for the postgres user -
> who I used to compile with didn't have /lib and /lib64 in it's path.  I
> don't see anything is configure.in or config.log to hint that pam isn't
> configured, but I'll re-configure anyway.  Is there a way to check PAM
> is configured with postgresql?  pam_unix2.so is located in
> /lib(64)/security.  I was wondering if both /lib and /lib/security
> needed to be in the $PATH or if just /lib/security was needed.

PATH isn't used for shared libs (/lib will be getting searched, or the 
machine probably wouldn't boot). There's a separate search path set for
the dynamic linker to load shared libraries, but it's platform specific.

(On a leenux you need to add the directory
to /etc/ld.so.conf - or you did last time i used it (circa redhat 5.2 ))

Or you could try setting LD_LIBRARY_PATH=/lib/security (that's a horrible
hack, but it should work).


If I was you I'd just add a --with-pam to your ./configure command line,
and check config.log after that completes.

To check this is your problem, try ldd - it
tells you what shared libs a binary is linked against (and uses the
search path I mentioned earlier).


Mine shows (freebsd 5.3):

rasputnik@eris:rasputnik$ ldd `which postmaster`
/usr/local/bin/postmaster:
        libintl.so.6 => /usr/local/lib/libintl.so.6 (0x28264000)
        libpam.so.2 => /usr/lib/libpam.so.2 (0x2826d000)
        libssl.so.3 => /usr/lib/libssl.so.3 (0x28274000)
        libcrypto.so.3 => /lib/libcrypto.so.3 (0x282a2000)
        libz.so.2 => /lib/libz.so.2 (0x28397000)
        libreadline.so.5 => /lib/libreadline.so.5 (0x283a7000)
        libcrypt.so.2 => /lib/libcrypt.so.2 (0x283d3000)
        libm.so.3 => /lib/libm.so.3 (0x283eb000)
        libutil.so.4 => /lib/libutil.so.4 (0x28405000)
        libc.so.5 => /lib/libc.so.5 (0x28411000)
        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x284eb000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x285d9000)


 
> Also, forget about PAM for a minute.

Bye then (I know jack about ident)!

-- 
'My life, and by extension everyone else's, is meaningless.'
		-- Bender
Rasputin :: Jack of All Trades - Master of Nuns



view thread (5+ messages)

Message-ID: <20050118212302.GM26970@lb.tenfour>
Permalink:  ../20050118212302.GM26970@lb.tenfour/
Also on:    postgresql.org/message-id/20050118212302.GM26970@lb.tenfour

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: rasputnik@hellooperator.net, KavanD@imsweb.com
  Subject: Re: PAM ldap
  In-Reply-To: <20050118212302.GM26970@lb.tenfour>
  References: <782D2A81EC812642B857B03B506E0B4432637F@granite.omni.imsweb.com> <20050118212302.GM26970@lb.tenfour>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox