PiFrame/ansible
PiFrame/ansible
1
0
Fork 0
Code Issues Releases Activity

Be more clear on which monit handler to call

Browse source
This commit is contained in:
KemoNine 2020-08-09 01:03:13 -04:00
parent 7d77b38355
commit 77c62cabd9
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
roles/monit/handlers/main.yml
View file

@ -5,6 +5,6 @@
state: "restarted" state: "restarted"
when: not monit_containerized when: not monit_containerized
- name: restart monit - name: restart monit containerized
command: /usr/bin/s6-svc -r /var/run/s6/services/monit command: /usr/bin/s6-svc -r /var/run/s6/services/monit
when: monit_containerized when: monit_containerized

6
roles/monit/tasks/dispatcher.yml
View file

@ -10,7 +10,7 @@
group: root group: root
mode: 0600 mode: 0600
notify: notify:
- restart monit - restart monit containerized
tags: tags:
- monit-config - monit-config
- name: Setup filesystem monitoring - name: Setup filesystem monitoring
@ -23,7 +23,7 @@
loop: loop:
"{{ monit_filesystems }}" "{{ monit_filesystems }}"
notify: notify:
- restart monit - restart monit containerized
tags: tags:
- monit-config - monit-config
- monit-filesystems - monit-filesystems
@ -36,7 +36,7 @@
mode: 0600 mode: 0600
when: monit_wireguard when: monit_wireguard
notify: notify:
- restart monit - restart monit containerized
tags: tags:
- monit-config - monit-config
- monit-wireguard - monit-wireguard