From: Frank Cusack <fcusack@fcusack.com>
To: "Mathias Fröhlich" <Mathias.Froehlich@web.de>,
"Jerry Cooperstein" <coop@axian.com>
Cc: linux-kernel@vger.kernel.org, Luke Howard <lukeh@PADL.COM>
Subject: Re: NPTL v userland v LT (RH9+custom kernel problem)
Date: Thu, 7 Aug 2003 22:45:45 -0700 [thread overview]
Message-ID: <20030807224545.A29285@google.com> (raw)
In-Reply-To: <200308071506.04890.Mathias.Froehlich@web.de>; from Mathias.Froehlich@web.de on Thu, Aug 07, 2003 at 03:06:04PM +0200
On Thu, Aug 07, 2003 at 03:06:04PM +0200, Mathias Fröhlich wrote:
> I think you can try out the nss_ldap rpm at
>
> http://na.uni-tuebingen.de/~frohlich/nss_ldap/
Didn't fix my problem. I'll dig in and narrow this down further.
On Thu, Aug 07, 2003 at 09:42:36AM -0500, Jerry Cooperstein wrote:
> If you read the release notes for RH9 you'll see you can adjust what
> thread library gets used with the environmental variable
> LD_ASSUME_KERNEL. So for instance you can do:
>
> LD_ASSUME_KERNEL=2.2.5 rpm ....
> LD_ASSUME_KERNEL=2.2.5 up2date
>
> (I've mentioned these two because I've noted these fail when you are
> root...)
Interesting. Something these have in common is that they all use
Berkeley db4 (up2date by virtue of using rpm). I don't understand why
nss_ldap or pam_ldap would, but it's one of the sources in the srpm.
But, rpm works for me (both RH and unpatched kernels).
/fc
next prev parent reply other threads:[~2003-08-08 5:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 8:39 NPTL v userland v LT (RH9+custom kernel problem) Frank Cusack
2003-08-07 8:49 ` Arjan van de Ven
2003-08-07 14:42 ` Jerry Cooperstein
2003-08-07 13:06 ` Mathias Fröhlich
2003-08-08 5:45 ` Frank Cusack [this message]
2003-08-08 6:02 ` Valdis.Kletnieks
2003-08-08 6:53 ` Peter Svensson
2003-08-08 7:10 ` Pau Aliagas
2003-08-08 10:32 ` Henning P. Schmiedehausen
2003-08-08 17:37 ` Frank Cusack
2003-08-08 19:05 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 13:20 Luke Howard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030807224545.A29285@google.com \
--to=fcusack@fcusack.com \
--cc=Mathias.Froehlich@web.de \
--cc=coop@axian.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukeh@PADL.COM \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.