2009/9/3 Thomas Bellman <[email protected]>: > > I'm trying to use a snapshot of the upcoming 0.25 release on nontrivial > manifests for the first time, and I'm having some problems. Specifically, > I'm using the stand-alone 'puppet' executable, and find that it seems to > ignore the --modulepath option. Or, for that matter, the modulepath > setting in puppet.conf. > > This is on CentOS 5.3, using a Git snapshot of Puppet (commit > e589cd39cc1d76de59cf4758bb986fa15f64571c). Stock 0.24.8 installed > from EPEL works as I expect. > > Setting the modulepath parameter in puppet.conf doesn't help either, > but setting the environment variable PUPPETLIB does. Am I missing > something that has intentionally been changed for 0.25, or is that > a bug?
Thomas I think that's a bug - can you log a ticket please. With full trace etc. Thanks James Turnbull -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
