.TH pumount 1 "August 27, 2004" "Martin Pitt"
pumount \- umount arbitrary hotpluggable devices as normal user
pumount is a wrapper around the standard umount program which permits normal
users to umount removable devices without a matching /etc/fstab entry.
pumount also supports encrypted devices which use dm-crypt and have
LUKS metadata. If a LUKS-capable
is installed, pumount will umount the mapped device instead and call
cryptsetup to close the decrypted device afterwards.
as its only argument. This will umount
from a directory below /media if policy is met (see below).
Please note that, as with
.BR pmount ,
you can use labels and uuids as described in
(5) for devices present in
.IR /etc/fstab .
In this case, the device name need to match exactly the corresponding
.IR /etc/fstab ,
.B \-l, \-\-lazy
Lazy unmount. Detach the filesystem from the filesystem hierarchy now,
and cleanup all references to the filesystem as soon as it is not busy
anymore. (Requires kernel 2.4.11 or later.)
.B IMPORTANT NOTES
This option should not be used unless you
know what you are doing, as chances are high that it will result in
data loss on the removable drive. Please run
manually and wait until it finishes. In addition,
a device which was unmounted lazily.
.IR cryptsetup (1))
did not open. However, you can bypass this restriction with this
flag. You probably will need it if you did mess around with the
.B \-h, \-\-help
Print a help message and exit successfully.
.B \-d, \-\-debug
Enable verbose debug messages.
Print the current version number and exit successfully.
The umount will succeed if all of the following conditions are met:
.IP \(bu 2
is a block device in /dev/ (it does not need to exist if
is not in /etc/fstab (if it is, pmount executes \fB umount \fI device\fR as the
calling user to handle this transparently)
is mounted according to /etc/mtab and /proc/mounts with the calling user's uid
mount point is in /media
.SH PUMOUNT AND MISSING DEVICES
now supports unmounting devices that have gone missing for some
reason, such as a brutal removal of the device, or a kernel/hardware
problem. Just specify the mount point as argument for
.SH SEE ALSO
.BR pmount (1),
.BR cryptsetup (1),
.BR umount (8)
is developed by Martin Pitt <email@example.com>.