http://reductivelabs.com/trac/puppet/ticket/793 I found the above bug while researching puppet environments. I would like to use environments and it occured to me that I could sidestep that bug by simply adding confdir=/etc/puppet/$environment to /etc/puppet/puppet.conf. However, I assume that would cause me a little bit of grief in other ways. If I run puppetd with the parameter --environment=development but don''t also specify the config file from the command line, what will happen if I send SIGHUP to puppetd? I''m guessing it will have used /etc/puppet/puppet.conf and only that config file when it first started but that HUP would make it read /etc/puppet/development/puppet.conf. If it''s true, then I suppose I''m better off just specifying the config file on the command line and setting the environment in there. -- Bruce --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Feb 13, 2009, at 11:35 AM, Bruce Richardson wrote:> > http://reductivelabs.com/trac/puppet/ticket/793 > > I found the above bug while researching puppet environments. I would > like to use environments and it occured to me that I could sidestep > that > bug by simply adding > > confdir=/etc/puppet/$environment > > to /etc/puppet/puppet.conf. However, I assume that would cause me a > little bit of grief in other ways. If I run puppetd with the > parameter > --environment=development but don''t also specify the config file from > the command line, what will happen if I send SIGHUP to puppetd? I''m > guessing it will have used /etc/puppet/puppet.conf and only that > config > file when it first started but that HUP would make it read > /etc/puppet/development/puppet.conf. > > If it''s true, then I suppose I''m better off just specifying the config > file on the command line and setting the environment in there.Why wouldn''t you just set your environment in the configuration file? And really, that bug isn''t much related, AFAICT; the environment should change if you change it in the configuration file. -- I worry that the person who thought up Muzak may be thinking up something else. -- Lily Tomlin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Fri, Feb 13, 2009 at 05:14:22PM -0600, Luke Kanies wrote:> > to /etc/puppet/puppet.conf. However, I assume that would cause me a > > little bit of grief in other ways. If I run puppetd with the > > parameter > > --environment=development but don''t also specify the config file from > > the command line, what will happen if I send SIGHUP to puppetd? I''m > > guessing it will have used /etc/puppet/puppet.conf and only that > > config > > file when it first started but that HUP would make it read > > /etc/puppet/development/puppet.conf. > > > > If it''s true, then I suppose I''m better off just specifying the config > > file on the command line and setting the environment in there. > > Why wouldn''t you just set your environment in the configuration file? >I thought I had explained that: it seems to me that if I set $confdir=/etc/puppet/$environment in the config file then $config is now ''/etc/puppet/development/puppet.conf'', which is NOT the file which puppet read when it first started. I expect this to be a potential trap in waiting - what happens if I now HUP puppetd, which file will it read?> And really, that bug isn''t much related, AFAICT ; the environment > should change if you change it in the configuration file.I''m trying to sidestep the effects of the bug. AIUI, the intended effect of setting $environment is that it adds (prefixes?) a bunch of important search paths with $confdir/$environment, but the bug means that this doesn''t happen for all of those paths. So I thought that simply changing $confdir to reflect the environment would sidestep this, because all of those paths *will* be changed if I globally change $confdir. I''m a little nervous of the side effects, though. -- Bruce I see a mouse. Where? There, on the stair. And its clumsy wooden footwear makes it easy to trap and kill. -- Harry Hill --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, Feb 17, 2009 at 02:02:30PM +0000, Bruce Richardson wrote:> that this doesn''t happen for all of those paths. So I thought that > simply changing $confdir to reflect the environment would sidestep this, > because all of those paths *will* be changed if I globally change > $confdir. I''m a little nervous of the side effects, though.Note: I gave up on that idea for other reasons, but I''m still interested to know what the effect would be. -- Bruce Those who cast the votes decide nothing. Those who count the votes decide everything. -- Joseph Stalin --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---