hm, I still don't see the logic. I think this is a common scenario (please tell me I'm wrong) that you ensure presence of a service generally, and then deploy a config file, and on changes you want - of course - the service to be restarted. or ... not?!
is there a puppet pattern on how to do this maybe? Thanks, Axel. Am Mittwoch, 5. September 2012 10:47:04 UTC+2 schrieb Axel Bock: > > Hi readers, > > I had this idea. I am deploying a configuration file of a service with > puppet, and I want to restart the service if the file changes. > > so I had this idea that the file definition contains a require=> and a > notify=> for the service. > that does not work, because Puppet does assume cyclic dependencies then. > > And I have no clue whatsoever why. both statements go from file to service > (or from service to file, however you like to put it), but I really don't > see a cyclic dependency here. > > > can anyone help me out? > thanks in advance, > axel. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5UpZmaf6vyMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
