renamed sv to runit, avoid svc confusion
This commit is contained in:
parent
693c176f43
commit
294a23d7f6
2 changed files with 3 additions and 2 deletions
|
@ -128,6 +128,7 @@ Ansible Changes By Release
|
|||
- packet:
|
||||
* packet_device
|
||||
* packet_sshkey
|
||||
- runit
|
||||
- smartos:
|
||||
* imgadm
|
||||
* vmadm
|
||||
|
|
|
@ -26,7 +26,7 @@ ANSIBLE_METADATA = {'status': ['stableinterface'],
|
|||
|
||||
DOCUMENTATION = '''
|
||||
---
|
||||
module: sv
|
||||
module: runit
|
||||
author: "James Sumners (@jsumners)"
|
||||
version_added: "2.3"
|
||||
short_description: Manage runit services.
|
||||
|
@ -45,7 +45,7 @@ options:
|
|||
commands unless necessary. C(restarted) will always bounce the
|
||||
service (sv restart) and C(killed) will always bounce the service (sv force-stop).
|
||||
C(reloaded) will send a HUP (sv reload).
|
||||
C(once) will run a normally downed svc once (sv once), not really
|
||||
C(once) will run a normally downed sv once (sv once), not really
|
||||
an idempotent operation.
|
||||
enabled:
|
||||
required: false
|
Loading…
Reference in a new issue