From: Luke Howard <lukeh@PADL.COM>
To: Mathias.Froehlich@web.de
Cc: linux-kernel@vger.kernel.org, fcusack@fcusack.com
Subject: Re: NPTL v userland v LT (RH9+custom kernel problem)
Date: Thu, 7 Aug 2003 23:20:21 +1000 [thread overview]
Message-ID: <200308071320.XAA79071@au.padl.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=US-ASCII, Size: 1007 bytes --]
Integrating this patch is on my todo list.
-- Luke
>From: Mathias =?utf-8?q?Fr=C3=B6hlich?= <Mathias.Froehlich@web.de>
>Subject: Re: NPTL v userland v LT (RH9+custom kernel problem)
>To: linux-kernel@vger.kernel.org
>Cc: fcusack@fcusack.com, Luke Howard <lukeh@padl.com>
>Date: Thu, 7 Aug 2003 15:06:04 +0200
>
>
>Hi,
>
>I think you can try out the nss_ldap rpm at
>
>http://na.uni-tuebingen.de/~frohlich/nss_ldap/
>
>It is built on RedHat 9.
>The main target of this rpm is to eliminate the recursive entrance bug of
>nss_ldap if the ldap host is not resolved before entering the ldap nss
>modules gethostbyname. But there is also some threading cleanup included.
>
>I don't know what the real reason of the reported problem is, but it does not
>occur since the time i use my patched nss_ldap module.
>I use both kinds of kernels with redhat 9 vanilla kernel.org and redhat
>modified ones.
>
> Hope this helps
>
> Mathias Fröhlich
>
>--
>Mathias Fröhlich, email: Mathias.Froehlich@web.de
>
>
next reply other threads:[~2003-08-07 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 13:20 Luke Howard [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=200308071320.XAA79071@au.padl.com \
--to=lukeh@padl.com \
--cc=Mathias.Froehlich@web.de \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
/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.