public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthias dot andree at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/430] nsswitch.conf doesn't support TRYAGAIN=forever, giving bogus results when NIS is not responding
Date: Sun, 18 Feb 2007 12:45:00 -0000 [thread overview]
Message-ID: <20070218124544.1207.qmail@sourceware.org> (raw)
In-Reply-To: <20041007145959.430.matthias.andree@gmx.de>
------- Additional Comments From matthias dot andree at gmx dot de 2007-02-18 12:45 -------
Drepper, try to stick to technical arguments rather than trying to bully people
who bring bad news. These messengers might eventually shout these inferior (to
put it mildly) bug handling policies, people involved and consequences even for
bug-free software from the rooftops. After all, you're not the assignee... and
I'm not at all impressed.
One of the issues mentioned here persists even with this newer glibc version, so
I'm setting "Version unspecified" since 2.5 isn't yet there in the bugzilla:
GNU C Library stable release version 2.5 (20061011), by Roland McGrath et al.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Configured for i686-suse-linux.
Compiled by GNU CC version 4.1.2 20061115 (prerelease) (SUSE Linux).
Compiled on a Linux 2.6.18 system on 2006-11-26.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
GNU libio by Per Bothner
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
NoVersion patch for broken glibc 2.0 binaries
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
Version|2.3.5 |unspecified
http://sourceware.org/bugzilla/show_bug.cgi?id=430
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2007-02-18 12:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 15:00 [Bug libc/430] New: " matthias dot andree at gmx dot de
2005-09-26 14:58 ` [Bug libc/430] " drepper at redhat dot com
2006-01-12 16:59 ` matthias dot andree at gmx dot de
2006-01-12 17:03 ` matthias dot andree at gmx dot de
2006-04-19 8:45 ` matthias dot andree at gmx dot de
2006-04-22 17:57 ` drepper at redhat dot com
2006-04-23 14:49 ` matthias dot andree at gmx dot de
2006-04-25 17:58 ` drepper at redhat dot com
2006-12-07 14:11 ` matthias dot andree at gmx dot de
2007-02-18 4:02 ` drepper at redhat dot com
2007-02-18 12:41 ` matthias dot andree at gmx dot de
2007-02-18 12:45 ` matthias dot andree at gmx dot de [this message]
2007-02-19 1:29 ` fche at redhat dot com
2007-02-19 1:42 ` matthias dot andree at gmx dot de
2010-06-01 3:11 ` pasky at suse dot cz
2010-06-01 8:20 ` matthias dot andree at gmx dot de
[not found] <bug-430-131@http.sourceware.org/bugzilla/>
2011-06-08 9:11 ` matthias.andree at gmx dot de
2011-06-08 9:12 ` matthias.andree at gmx dot de
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=20070218124544.1207.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).