From 8df7462688d6ed8e2145438f6105668477a2e814 Mon Sep 17 00:00:00 2001
From: rmacklem <rmacklem@FreeBSD.org>
Date: Tue, 31 May 2011 18:27:18 +0000
Subject: Add a sentence to the umount.8 man page to clarify the behaviour for
 forced dismount when used on an NFS mount point. Requested by Jeremy
 Chadwick. This is a content change.

MFC after:	2 weeks
---
 sbin/umount/umount.8 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

(limited to 'sbin/umount/umount.8')

diff --git a/sbin/umount/umount.8 b/sbin/umount/umount.8
index 91231a7..cb3a97b 100644
--- a/sbin/umount/umount.8
+++ b/sbin/umount/umount.8
@@ -28,7 +28,7 @@
 .\"     @(#)umount.8	8.2 (Berkeley) 5/8/95
 .\" $FreeBSD$
 .\"
-.Dd July 18, 2003
+.Dd May 31, 2011
 .Dt UMOUNT 8
 .Os
 .Sh NAME
@@ -78,6 +78,9 @@ The file system is forcibly unmounted.
 Active special devices continue to work,
 but all other files return errors if further accesses are attempted.
 The root file system cannot be forcibly unmounted.
+For NFS, a forced dismount can take up to 1 minute or more to
+complete against an unresponsive server and may throw away
+data not yet written to the server for this case.
 .It Fl h Ar host
 Only file systems mounted from the specified host will be
 unmounted.
-- 
cgit v1.1