Date: 29 Oct 1997 03:28:35 -0000 From: mmead@goof.com To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/4884: the version of amd in 2.2.5-RELEASE appears to exercise a bug in yp_order Message-ID: <19971029032835.1729.qmail@goof.com> Resent-Message-ID: <199710290330.TAA15025@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4884 >Category: bin >Synopsis: the version of amd in 2.2.5-RELEASE appears to exercise a bug in yp_order >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 28 19:30:01 PST 1997 >Last-Modified: >Originator: matthew c. mead >Organization: Goof Telecommunications >Release: FreeBSD 2.2.5-RELEASE i386 >Environment: FreeBSD machine running amd is 2.2.5-RELEASE with either ypserv running or an NIS+ server in NIS compatibility mode running on a Solaris 2.5.1 machine. Either NIS environment produces the error. >Description: When asking amd to use a map from NIS for the automounting of directories, amd logs "No source data for map amd.home". Further investigation appears to point at a bug in yp_order which causes amd to never load the map. >How-To-Repeat: setup NIS server create map amd.home populate amd.home with a valid amd map invoke amd: amd -r -y `domainname` -l syslog /home amd.home >Fix: Unknown at this time - however, changing amd so that it simply reloads the map if it's been more than 600 seconds since las reload causes amd to happily use the NIS map. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971029032835.1729.qmail>