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
07d5b50e2c
commit
30be06c971
1 changed files with 4 additions and 4 deletions
|
@ -51,14 +51,14 @@ options:
|
|||
default: null
|
||||
dump:
|
||||
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
|
||||
default: null
|
||||
default: 0
|
||||
passno:
|
||||
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
|
||||
default: null
|
||||
default: 0
|
||||
state:
|
||||
description:
|
||||
- If C(mounted) or C(unmounted), the device will be actively mounted or unmounted
|
||||
|
|
Loading…
Reference in a new issue