mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Setting the actual passno and dump defaults, and warning user of consequences in nulling
Using ansible 1.8.4, I found that these two options actually work slightly different than advertised.
This commit is contained in:
parent
ba90eea165
commit
00613cd4f3
1 changed files with 4 additions and 4 deletions
|
@ -51,14 +51,14 @@ options:
|
||||||
default: null
|
default: null
|
||||||
dump:
|
dump:
|
||||||
description:
|
description:
|
||||||
- dump (see fstab(8))
|
- "dump (see fstab(8)), Note that if nulled, C(state=present) will cease to work and duplicate entries will be made with subsequent runs."
|
||||||
required: false
|
required: false
|
||||||
default: null
|
default: 0
|
||||||
passno:
|
passno:
|
||||||
description:
|
description:
|
||||||
- passno (see fstab(8))
|
- "passno (see fstab(8)), Note that if nulled, C(state=present) will cease to work and duplicate entries will be made with subsequent runs."
|
||||||
required: false
|
required: false
|
||||||
default: null
|
default: 0
|
||||||
state:
|
state:
|
||||||
description:
|
description:
|
||||||
- If C(mounted) or C(unmounted), the device will be actively mounted or unmounted
|
- If C(mounted) or C(unmounted), the device will be actively mounted or unmounted
|
||||||
|
|
Loading…
Reference in a new issue