It might make sense in some cases, but in others it is counter productive: For example, admin A is configuring the tomcat.xml file, admin B is adding a new dev user, they should not lock each other.
On Wed, Jun 10, 2015 at 10:56 AM, Adam Kosmin <[email protected]> wrote: > Greets, > > I'm coming into Ansible from a Puppet background and have questions with > regard to whether or not the idea of "lock files" is even appropriate. As > I'm sure many here know, the puppet agent handled creating this file in > order to avoid multiple overlapping runs. Of course, that's a completely > different model (client/server) but I'd be really interested to hear back > from this community on this topic. Given that Ansible is essentially just > firing out commands over ssh in a serial fashion, I personally see no need > for lock files. Of course, I could be missing something..... > > thoughts, considerations, use cases, and further questions welcome.... > > Best, > Adam > > -- > 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/9751fb53-cd98-4854-be40-660dbeb85e13%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Brian Coca -- 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/CAJ5XC8na1CGHj5TeiX93BgUKv2k4d5SYxqQDUA5tb4gm-eo1Rw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
