ansible-roles/supysonic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

delete socket handler

Browse Source
This commit is contained in:
vincent 2019-05-13 20:05:11 +02:00
parent 6010d2aa4f
commit 28aed2d153
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
handlers/main.yml
View File

@ -7,12 +7,6 @@
daemon_reload: yes daemon_reload: yes
become: yes become: yes
- name: ensure socket is start
systemd:
name: "gunicorn-{{supysonic_name}}.socket" # not required. Name of the service. When using in a chroot environment you always need to specify the full name i.e. (crond.service).
enabled: true # not required. Whether the service should start on boot. B(At least one of state and enabled are required.)
state: restarted # not required. choices: reloaded;restarted;started;stopped. C(started)/C(stopped) are idempotent actions that will not run commands unless necessary. C(restarted) will always bounce the service. C(reloaded) will always reload.
become: yes
- name: restart supysonic service - name: restart supysonic service
systemd: systemd: