From: Chip Salzenberg <chip@debian.org>
To: Juergen Kreileder <jk@blackdown.de>
Cc: nfs@lists.sourceforge.net, 202756@bugs.debian.org
Subject: Re: [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 13:22:53 -0400 [thread overview]
Message-ID: <20030920172253.GD14640@perlsupport.com> (raw)
In-Reply-To: <87r82cj9h6.fsf@zaphod.blackdown.de>
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?
Or is that not a practical test for you?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-20 17:23 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 [this message]
2003-09-20 18:01 ` Juergen Kreileder
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=20030920172253.GD14640@perlsupport.com \
--to=chip@debian.org \
--cc=202756@bugs.debian.org \
--cc=jk@blackdown.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox