Hmm, if that's enough to make it reread all the nodes, then I suppose I could have my git hook scripts that syncs the puppet manifests from my git repo always touch the site.pp file after it fires. Any other good methods for handling this?
On Jun 23, 4:05 pm, Aaron Grewell <[email protected]> wrote: > touch site.pp? > On Jun 23, 2011 1:01 PM, "Pheran" <[email protected]> wrote:> So, instead of > defining all my nodes in one file, I use what seems to > > be a fairly common practice, from site.pp I do: > > > import 'nodes/*' > > > Then I have a nodes directory containing a .pp file for each node. > > The only problem with this setup is that puppet seems oblivious to new > > node files in the nodes directory until you do a "service puppetmaster > > restart". Is there any way to have puppet automatically find those > > new files without restarting? Alternately, does anyone have a good > > method for automating the necessary restart? Thanks. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group.> To post to this group, send email to > [email protected]. > > To unsubscribe from this group, send email to > > [email protected].> For more options, visit this > group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
