Date: Wed, 8 Jan 2003 14:18:01 +0100 (CET) From: Matthias Andree <matthias.andree@web.de> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/46867: NIS-based getpwent() falsely returns NULL Message-ID: <200301081318.h08DI1Lc000560@libertas.emma.line.org>
next in thread | raw e-mail | index | archive | help
>Number: 46867 >Category: bin >Synopsis: NIS-based getpwent() falsely returns NULL >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 08 06:00:09 PST 2003 >Closed-Date: >Last-Modified: >Originator: Matthias Andree >Release: FreeBSD 4.7-STABLE i386 >Organization: >Environment: System: FreeBSD libertas.emma.line.org 4.7-STABLE FreeBSD 4.7-STABLE #11: Wed Jan 8 01:47:45 CET 2003 toor@libertas.emma.line.org:/usr/src/sys/compile/LIBERTAS i386 >Description: When NIS is enabled e. g. for passwd lookups, and the NIS server goes down, the NIS domains goes unbound, NIS-based lookups will falsely fail after 200 seconds (40 retries). The getpwnam interface (and other similar interfaces) have no means of returning a temporary error, and applications do not expect temporary results. As a consequence, the application returns "no such user" when the user is in fact present, only his/her passwd entry is temporarily inaccessible. -su-2.05b# time id -u nbin id: nbin: no such user real 3m20.443s user 0m0.020s sys 0m0.026s This can, for example, cause mail to bounce when the NIS server goes down. >How-To-Repeat: >Fix: NEVER let NIS-based lookups time out. (Solaris also retries forever.) >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301081318.h08DI1Lc000560>