Apologies, I didn't notice the wiki had been updated. I'd expect that behaviour if using a before, but really think a notify shouldn't cause such a dependency, as i'm only asking for a restart/reload. That's just my two pence worth.
I'll go back to using includes. Thanks, Matt 2009/11/2 Peter Meier <peter.me...@immerda.ch>: > >> err: Could not apply complete catalog: Found dependency cycles in the >> following relationships: File[/etc/nginx/nginx.conf] => >> Service[nginx], Service[nginx] => File[/etc/nginx/nginx.conf]; try >> using the '--graph' option and open the '.dot' files in OmniGraffle or >> GraphViz >> >> If I comment out the notify it works :-( > > the problem is that require implies that every resource in this class > has to be satisfied before the current class is evaluated, which means > more or less that every resource in the class my-nginx gets a require > on the class nginx and its resources. The behavior you encounter is > explicitly documented as a warning on [1]. So it works properly and > your problem is even documented. > What you need to do is to change the require into an include and > require the package for the file and still notify the service. Like > that your file definition will be waved into the dependency graph > between package and service, hence the ordering is correct. > > cheers pete > > [1] http://reductivelabs.com/trac/puppet/wiki/FunctionReference#require > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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 -~----------~----~----~----~------~----~------~--~---
