f9ee10c7bb
/sbin/umount does not return the correct exit status due to incorrect logic in its internals. Further, because of the nature of the code, you *cannot* use it to umount a directory from a union mountpoint. Well, you can sometimes, it depends on if the directory is at the top of the union stack or not :) Submitted by: njw@cs.city.ac.uk (Nick Williams)
146 lines
4.2 KiB
Groff
146 lines
4.2 KiB
Groff
.\" Copyright (c) 1980, 1989, 1991, 1993
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
.\" must display the following acknowledgement:
|
|
.\" This product includes software developed by the University of
|
|
.\" California, Berkeley and its contributors.
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
.\" may be used to endorse or promote products derived from this software
|
|
.\" without specific prior written permission.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" @(#)umount.8 8.1 (Berkeley) 2/20/94
|
|
.\"
|
|
.Dd February 20, 1994
|
|
.Dt UMOUNT 8
|
|
.Os BSD 4
|
|
.Sh NAME
|
|
.Nm umount
|
|
.Nd unmount file systems
|
|
.Sh SYNOPSIS
|
|
.Nm umount
|
|
.Op Fl fv
|
|
.Ar special | node
|
|
.Nm umount
|
|
.Fl a
|
|
.Op Fl fv
|
|
.Op Fl h Ar host
|
|
.Op Fl t Ar ufs | lfs | external_type
|
|
.Sh DESCRIPTION
|
|
The
|
|
.Nm umount
|
|
command
|
|
calls the
|
|
.Xr unmount 2
|
|
system call to remove a
|
|
.Ar "special device"
|
|
or the remote node (rhost:path) from the file system tree at the point
|
|
.Ar node .
|
|
If either
|
|
.Ar special
|
|
or
|
|
.Ar node
|
|
are not provided, the appropriate information is taken from the
|
|
.Xr fstab 5
|
|
file.
|
|
.Pp
|
|
The options are as follows:
|
|
.Bl -tag -width indent
|
|
.It Fl a
|
|
All of the file systems described in
|
|
.Xr fstab 5
|
|
are unmounted.
|
|
.It Fl f
|
|
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.
|
|
.It Fl h Ar host
|
|
Only filesystems mounted from the specified host will be
|
|
unmounted.
|
|
This option is implies the
|
|
.Fl a
|
|
option and, unless otherwise specified with the
|
|
.Fl t
|
|
option, will only unmount NFS filesystems.
|
|
.It Fl t Ar "ufs \\*(Ba lfs \\*(Ba external type"
|
|
Is used to indicate the actions should only be taken on
|
|
filesystems of the specified type.
|
|
More than one type may be specified in a comma separated list.
|
|
The list of filesystem types can be prefixed with
|
|
.Dq no
|
|
to specify the filesystem types for which action should
|
|
.Em not
|
|
be taken.
|
|
For example, the
|
|
.Nm umount
|
|
command:
|
|
.Bd -literal -offset indent
|
|
umount -a -t nfs,mfs
|
|
.Ed
|
|
.Pp
|
|
umounts all filesystems of the type
|
|
.Tn NFS
|
|
and
|
|
.Tn MFS .
|
|
.It Fl v
|
|
Verbose, additional information is printed out as each file system
|
|
is unmounted.
|
|
.El
|
|
.Sh FILES
|
|
.Bl -tag -width /etc/fstab -compact
|
|
.It Pa /etc/fstab
|
|
file system table
|
|
.El
|
|
.Sh SEE ALSO
|
|
.Xr unmount 2 ,
|
|
.Xr fstab 5 ,
|
|
.Xr mount 8
|
|
.Sh BUGS
|
|
When using union filesystems,
|
|
.Xr umount 8
|
|
cannot always determine the node which is the mountpoint.
|
|
In this case,
|
|
it is necessary to specify the relevant directory to be unmounted
|
|
in the same form as that displayed by
|
|
.Xr mount 8 .
|
|
For example, given a mount entry like this:
|
|
.Bd -literal -offset indent
|
|
<above>/tmpdir on /cdrom (local, user mount)
|
|
.Ed
|
|
.Pp
|
|
then the command:
|
|
.Bd -literal -offset indent
|
|
umount '<above>/tmpdir'
|
|
.Ed
|
|
.Pp
|
|
would unmount
|
|
.Ar /tmpdir
|
|
from the mountpoint
|
|
.Ar /cdrom .
|
|
.Sh HISTORY
|
|
A
|
|
.Nm umount
|
|
command appeared in
|
|
.At v6 .
|