Date: Tue, 21 Mar 2000 18:59:57 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: FreeBSD-gnats-submit@freebsd.org Subject: conf/17540: NIS host lookups cause NFS mounts to wedge at boot Message-ID: <200003212359.SAA06408@grasshopper.cs.duke.edu>
next in thread | raw e-mail | index | archive | help
>Number: 17540 >Category: conf >Synopsis: NIS host lookups cause NFS mounts to wedge at boot >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 21 16:10:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Andrew Gallatin >Release: FreeBSD 4.0-RELEASE i386 >Organization: >Environment: FreeBSD 4.0-RELEASE as an NIS client, static NFS mounts out of /etc/fstab, and nis first in /etc/host.conf >Description: Portmap is not started until until the pass2 portion of rc.network is executed. However, network_pass2 is run after we mount NFS filesystems. This is problematic in some environments if you have have nis as one of the 1st entries in the host search order in /etc/host.conf. The problem is that the resolver cannot contact portmap to realize that ypbind isn't available. So the machines sits at Mounting NFS file systems. for quite some time. Long enough for somebody to assume the machine is wedged. >How-To-Repeat: Change /etc/host.conf so that nis is first in the search order, add an nfs mount to /etc/fstab, reboot. >Fix: Start portmap before attempting any NFS mounts. I suppose a shorter timeout when portmap cannot be contacted would also be a good fix. >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?200003212359.SAA06408>