Date: 7 Mar 2007 22:56:57 -0000 From: Mike Meyer <mwm@mired.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/110062: mount_nfs doc fails to mention a failure condition Message-ID: <20070307225657.14031.qmail@mired.org> Resent-Message-ID: <200703072330.l27NU2I2049114@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 110062 >Category: docs >Synopsis: mount_nfs doc fails to mention a failure condition >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 07 23:30:01 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Mike Meyer >Release: FreeBSD 6.1-STABLE amd64 >Organization: Meyer Consulting >Environment: System: FreeBSD bhuda.mired.org 6.1-STABLE FreeBSD 6.1-STABLE #3: Mon Jan 1 15:13:18 EST 2007 mwm@bhuda.mired.org:/usr/src/sys/amd64/compile/BHUDA amd64 >Description: mount_nfs can fail to mount even critical file systems under some conditions. >How-To-Repeat: Try mounting mounting a file system from a non-existent host. >Fix: Well, the bug should be fixed in mount_nfs, but mentioning it in the man page seems at least appropriate for now. The attached patch to mount_nfs.8 adds that. --- mount_nfs.8 Wed Mar 7 17:52:14 2007 +++ mount_nfs.8-new Wed Mar 7 17:54:48 2007 @@ -347,3 +347,9 @@ but unfortunately this is restricted to mostly .Bx 4.4 servers. +.Pp +If the host name lookup failed, the mount fails irregardless of the +.FL b +and +.Fl R +flags. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070307225657.14031.qmail>