Tracking files that are not the normal side effect of a command are a poor way to track if a command was executed, the best way is to track the expected side effect of such a command (creates/removes does this by assuming those files are created/removed by the command's execution). There are other side effects that you can track, but hard to build them all into the command/shell modules (open port/service running/package installed/etc) but there are plenty of other actions that can query this. -- ---------- Brian Coca
-- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CACVha7dXu8pEBMU4PnhbYStTLp2B8T2A-mFG76EbPu62UXOK9Q%40mail.gmail.com.
