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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
