Fix absent state documentation

This commit is contained in:
NdFeB 2022-03-12 15:25:38 +01:00
parent 62d060a173
commit 211e6c74b5

View file

@ -32,6 +32,7 @@ options:
description: description:
- Device (or NFS volume, or something else) to be mounted on I(path). - Device (or NFS volume, or something else) to be mounted on I(path).
- Required when I(state) set to C(present) or C(mounted). - Required when I(state) set to C(present) or C(mounted).
- Ignored when I(state) set to C(absent) or C(unmounted).
type: path type: path
fstype: fstype:
description: description:
@ -68,9 +69,13 @@ options:
- If C(unmounted), the device will be unmounted without changing I(fstab). - If C(unmounted), the device will be unmounted without changing I(fstab).
- C(present) only specifies that the device is to be configured in - C(present) only specifies that the device is to be configured in
I(fstab) and does not trigger or require a mount. I(fstab) and does not trigger or require a mount.
- C(absent) specifies that the device mount's entry will be removed from - C(absent) specifies that the mount point entry I(path) will be removed
I(fstab) and will also unmount the device and remove the mount from I(fstab) and will also unmount the mounted device and remove the
point. mount point. A mounted device will be unmounted regardless of I(src) or its
real source. C(absent) does not unmount recursively, and the module will
fail if multiple devices are mounted on the same mount point. Using
C(absent) with a mount point that is not registered in the I(fstab) has
no effect. Use C(unmounted) instead.
- C(remounted) specifies that the device will be remounted for when you - C(remounted) specifies that the device will be remounted for when you
want to force a refresh on the mount itself (added in 2.9). This will want to force a refresh on the mount itself (added in 2.9). This will
always return changed=true. If I(opts) is set, the options will be always return changed=true. If I(opts) is set, the options will be