[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: slapd problem



That will work with slapd, but not with the PAM LDAP modules.  These are
called behind the scenes on demand by a mechanism that's fairly subtle.

Simon


> -----Original Message-----
> From: Randy Kunkee [mailto:kunkee@neosoft.com]
> Sent: 04 October 2000 18:21
> To: Simon.Ritchie@net.ntl.com
> Cc: Christopher Cardinal; openldap-software@OpenLDAP.org
> Subject: Re: slapd problem
>
>
> Or, before running configure add a suitable -R flag to add the needed
> shared lib directories to the executables, eg.
>
> LDFLAGS="-R /usr/local/lib"
>
> Other OSs may have different ways of doing this.  Consult your man page
> for ld.
>
> Randy
>
>
> >
> >
> > > -----Original Message-----
> > > From: owner-openldap-software@OpenLDAP.org
> > > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Christopher
> > > Cardinal
> > > Sent: 04 October 2000 15:34
> > > To: openldap-software@OpenLDAP.org
> > > Subject: slapd problem
> > >
> > >
> > > On Solaris 2.6, when I run slapd, I get:
> > >
> > > /usr/local/libexec/slapd
> > > ld.so.1: /usr/local/libexec/slapd: fatal: libgdbm.so.2: open
> > > failed: No such
> > > file or directory
> > > Killed
> > >
> > > So I then run:
> > >
> > > env LD_LIBRARY_PATH=/var/usr_local/lib /usr/local/libexec/slapd
> > > and it works fine.
> > >
> > > So, did I miss something at compile time? I don't really
> > > understand that env
> > > variable. I guessed it from reading all the README's and
> > > INSTALL's I could
> > > find.
> >
> > I think that this relates to a problem I described in my
> previous posting,
> > but I am using Linux and your are seeing the Solaris version.  The
> > installation has set up some extra shared libraries in a
> directory that the
> > system doesn't know about, and you have to tell it where they
> are.  That's
> > the purpose of the variable.  Under Linux, you have to run a
> program called
> > ldconfig.
> >
> > Simon
> >
> >
>
>