All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Kreileder <jk@blackdown.de>
To: Chip Salzenberg <chip@debian.org>
Cc: nfs@lists.sourceforge.net, 202756@bugs.debian.org
Subject: Bug#202756: [jk@blackdown.de: Re: Bug#202756: nfs-kernel-server: 1.0.5-1 works with libc6 from unstable but fails with libc6 2.3.2-1 from experimental]
Date: Sat, 20 Sep 2003 20:01:27 +0200	[thread overview]
Message-ID: <87brtf9w5k.fsf@zaphod.blackdown.de> (raw)
In-Reply-To: <20030920172253.GD14640@perlsupport.com> (Chip Salzenberg's message of "Sat, 20 Sep 2003 13:22:53 -0400")

Chip Salzenberg <chip@debian.org> writes:

> According to Juergen Kreileder:
>> Chip Salzenberg <chip@pobox.com> writes:
>>> * 1.0.6 does _not_ fix the crash.
>>> * preloading libpthread.so.0 is still an effective workaround
>>
>> Looks like a glibc problem, it's triggered by using lwres in
>> nsswitch.conf.  See
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211621
>
> Ah, that's excellent news from our end.
>
> Have you verified that avoiding lwres allows mountd to keep working?

Yes, mountd works fine when I disable lwres.


        Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/

      reply	other threads:[~2003-09-20 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  2:14 Bug#202756: [jk@blackdown.de: Re: Bug#202756: nfs-kernel-server: 1.0.5-1 works with libc6 from unstable but fails with libc6 2.3.2-1 from experimental] Chip Salzenberg
2003-09-20  5:48 ` Juergen Kreileder
2003-09-20 17:22   ` Chip Salzenberg
2003-09-20 18:01     ` Juergen Kreileder [this message]

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=87brtf9w5k.fsf@zaphod.blackdown.de \
    --to=jk@blackdown.de \
    --cc=202756@bugs.debian.org \
    --cc=chip@debian.org \
    --cc=nfs@lists.sourceforge.net \
    /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.