From 7254d8812d2f313837309a8498bce7a1f844149d Mon Sep 17 00:00:00 2001 From: Steve French Date: Thu, 28 Apr 2005 04:21:42 +0000 Subject: Fix umount.cifs.8 build break (This used to be commit aae9cb6a427249e7362e1e8752216db9346a45df) --- docs/manpages/umount.cifs.8.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/manpages/umount.cifs.8.xml b/docs/manpages/umount.cifs.8.xml index fe14a81113..66aa2714c6 100644 --- a/docs/manpages/umount.cifs.8.xml +++ b/docs/manpages/umount.cifs.8.xml @@ -86,7 +86,7 @@ For more information see the kernel file fs/cifs/README. At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (unmounts of a cifs mount and another type of filesystem mount at the same time. - If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although only actually unmount the last one), rather than only removing the last matching entry in /etc/mtab. The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts. + If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although only actually unmount the last one), rather than only removing the last matching entry in /etc/mtab. The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts. Note that the typical response to a bug report is a suggestion -- cgit