Some library and packaging advice please?
Neil Joseph Schelly
neil at jenandneil.com
Wed May 28 19:28:21 EDT 2008
On Wednesday 28 May 2008 19:16, VirginSnow at vfemail.net wrote:
> > For all our servers, we have LDAP logins enabled for SSH logins,
> > monitoring
>
> Do you mean in PAM or SSH? Both?
PAM and NSS.
> > Here's my explanation of what's happening. When you start a process,
> > glibc is loaded as part of that process. glibc can also bring in other
> > auxiliary libraries, as needed. In particular, any libraries used for
> > NSS
>
> This makes me suspicious. Above (1), you stated that everything under
> /kolab was statically linked.
glibc is not statically linked. It uses the system glibc, but all other
library dependencies are statically filled by libraries in /kolab.
> > the /kolab bubble, it has libldap_r.a compiled into it statically, albeit
> > a slightly different version. This causes a duplication of all the
> > library functions in the run-time process now.
>
> With "bubble" installs like this, you usually have to modify the
> LD_LIBRARY_PATH environment variable (typically done in a "wrapper"
> shell script) before exec'ing the executable.
That's great if the binaries are using shared libraries and LD for loading
them. In this case, glibc is used to loading up the process, but the process
itself will not load any libraries.
> > Kolab-distributed OpenLDAP sources, but to use the libraries that come
> > with Debian to no avail. The dependencies spider out from there to
> > things like sasl, gnutls, gcrypt,
>
> If you know your Debian Magic well enough, you might be able to get
> away with taking the .spec file from the Debian source, dropping it in
> the new source tree, and tweaking it until it builds.
That's not a bad idea - I hadn't considered that yet.
> Hm (2). You're not building/installing this package as root, are you?
Actually, yes. But again, that's the way this particular bubble works. It
needs to create users and groups and such in the process of installing. That
said, it's on an otherwise clean install and on an isolated machine until I
can get these issues resolved.
-N
More information about the gnhlug-discuss
mailing list