<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Handler on ads' corner</title><link>https://andreas.scherbaum.la/tags/handler/</link><description>Recent content in Handler on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 29 Jul 2024 00:41:11 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/handler/index.xml" rel="self" type="application/rss+xml"/><item><title>Ansible Handler: respond to multiple different Notifications simultaneously</title><link>https://andreas.scherbaum.la/post/2024-07-29_ansible-handler-respond-to-multiple-different-notifications-simultaneously/</link><pubDate>Mon, 29 Jul 2024 00:41:11 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-07-29_ansible-handler-respond-to-multiple-different-notifications-simultaneously/</guid><description>&lt;p&gt;&lt;em&gt;Ansible&lt;/em&gt; has a concept of &amp;ldquo;handlers&amp;rdquo;, which run at the end of a Playbook, when something changed. In certain situations it might be desired or necessary to have a handler listen to more than one signal name. In my example: I&amp;rsquo;m updating the &lt;em&gt;Samba&lt;/em&gt; configuration, and before restarting &lt;code&gt;smbd&lt;/code&gt; or &lt;code&gt;nmbd&lt;/code&gt; I want to check the configuration. This &lt;em&gt;configuration check&lt;/em&gt; handler must listen to both restart signals.&lt;/p&gt;</description></item></channel></rss>