# Best practice for soemthing like "systemctl daemon-reload"?

**URL:** <https://forum.ansible.com/t/best-practice-for-soemthing-like-systemctl-daemon-reload/20476>\
**Category:** Ansible Project\
**Created:** [February 7, 2016, 1:26am UTC](https://forum.ansible.com/t/best-practice-for-soemthing-like-systemctl-daemon-reload/20476 "2016-02-07T01:26:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakov\_Sosic](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@Jakov\_Sosic](https://forum.ansible.com/u/Jakov_Sosic)\
**Post date:** [February 7, 2016, 1:26am UTC](https://forum.ansible.com/t/best-practice-for-soemthing-like-systemctl-daemon-reload/20476/1 "2016-02-07T01:26:49Z")

</div>

Hi guys.

I'm wondering on how to tackle `systemd` with ansible. Problem is that if I deploy or change systemd unit file with ansible, just managing service won't do it because `systemctl daemon-reload` have to run for systemd to read new service configuration.

There are two approaches I can think of.

1. Have a handler like this:

roles/elasticsearch/handlers/main.yml: