I am having a great deal of trouble using a custom fact in a module and I am
hoping someone can help me out.
I am using facter-1.5.0-2.el4 and puppet-0.24.5-1.el4. I know these are
really old versions.
The custom fact is defined using an environmental variable
export FACTER_VERTICAL="dev fit"
looks like a better way to get facts in:
> >> http://projects.puppetlabs.com/projects/1/wiki/Adding_Facts
> >>
> >> This will allow you to get some level of synchronization of your custom
> >> facts from your master to your clients in a much cleaner way.
> >&g
server means the hardware that the puppet client manages
On Tue, Nov 9, 2010 at 9:06 PM, Patrick wrote:
>
> On Nov 9, 2010, at 6:01 PM, Edward Bailey wrote:
>
> The purpose behind setting up the fact this way is that I thought it would
> be an easy way to populate servers with
>> because
> >> >> daemon will run as its own process with its own environment, so just
> >> >> exporting the variable will only effect your current running
> >> >> environment and
> >> >> not the puppet daemon environment. As s
Is their a mcollective rpm for rhel4? If not, is their a src rpm for 1.0 I
can compile for rhel4? I looked around the web site and could not find
anything.
Thanks
Ed
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send e
Hello
I am working on migrating from a working mongrel based puppet server to a
passenger based puppet server and I need some help. I am still getting some
errors that I can't explain and I hope someone knows what I am doing wrong.
I have installed the following to setup passenger
gem list
***
To explain the background behind my question
We have a number of situations where it would be great if I could have
puppet automatically maintain a symlink for a resource such as the Java JVM.
For example - we install the JDK in /usr/java so after the RPM install, the
path to the JVM is /usr/ja
