"is called twice for the same machine, one for the first group, one for the second."
This is not the case actually, but handlers are notified on a play by play basis. On Sat, Sep 20, 2014 at 5:25 AM, Olivier Javaux <[email protected]> wrote: > Another solution is to use set_fact to set a flag: false at the beginning, > and handler set it to true if modifications are done. > At the end, do the last action when flag is true. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/bbfee0ee-92d6-49db-9e04-8b26d8c6f674%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/bbfee0ee-92d6-49db-9e04-8b26d8c6f674%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxUJWOE9NU_CJeYnmkeXR98O_Rbnn%3Dq6qSJZ1i2BWX7tw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
