This is the mail archive of the glibc-bugs@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/430] New: nsswitch.conf doesn't support TRYAGAIN=forever, giving bogus results when NIS is not responding


The nsswitch.conf mechanism doesn't support a TRYAGAIN=forever switch which is
necessary to properly support NIS and similar services with the limited getpw*()
interface.

Problem: an application calling getpwnam() has no means to detect that it got
NULL because NIS was failed (NIS server dropped dead, whatever), which is a
temporary failure, rather than because the user was nonexistent.

Consequences: applications can wreak havoc if they are told "no such user" when
in fact the user exists but the information was temporarily unavailable. The
result may be that mail bounces, with the computer claiming the addressee were
non-existent, users being unsubscribed from mailing lists, users being unable to
log in and similar.

Suggested fix: Add an option TRYAGAIN=forever for nsswitch.conf that lets it
spin on the service that returned TRYAGAIN until it returns some different
condition, and make it the default for services such as nis that can exhibit
this problem. This will avoid returning temporary results.

Cross-Reference:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/46866

-- 
           Summary: nsswitch.conf doesn't support TRYAGAIN=forever, giving
                    bogus results when NIS is not responding
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: critical
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: matthias dot andree at gmx dot de
                CC: glibc-bugs at sources dot redhat dot com
  GCC host triplet: i686-suse-linux


http://sources.redhat.com/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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]