2015-02-02 12:34:26 -05:00
|
|
|
.Dd February 2, 2015
|
|
|
|
|
.Dt RMMOD 8
|
|
|
|
|
.Os ubase
|
|
|
|
|
.Sh NAME
|
|
|
|
|
.Nm rmmod
|
|
|
|
|
.Nd remove a module from the Linux kernel
|
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
|
.Nm
|
|
|
|
|
.Op Fl fw
|
|
|
|
|
.Ar module...
|
|
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
.Nm
|
|
|
|
|
removes one or more modules from the kernel.
|
|
|
|
|
.Sh OPTIONS
|
|
|
|
|
.Bl -tag -width Ds
|
|
|
|
|
.It Fl f
|
2014-04-12 10:21:11 -04:00
|
|
|
This option can be extremely dangerous: it has no effect unless
|
|
|
|
|
CONFIG_MODULE_FORCE_UNLOAD was set when the kernel was compiled.
|
|
|
|
|
With this option, you can remove modules which are being used, or
|
|
|
|
|
which are not designed to be removed, or have been marked as unsafe.
|
2015-02-02 12:34:26 -05:00
|
|
|
.It Fl w
|
|
|
|
|
Normally,
|
|
|
|
|
.Nm
|
|
|
|
|
will refuse to unload modules which are in
|
|
|
|
|
use. With this option,
|
|
|
|
|
.Nm
|
|
|
|
|
will isolate the module, and wait until the module is no longer used. Noone
|
|
|
|
|
new will be able to use the module, but it's up to you to make sure the
|
|
|
|
|
current users eventually finish with it.
|
|
|
|
|
.El
|
|
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr insmod 8 ,
|
|
|
|
|
.Xr lsmod 8
|
