If I remove the extension .rb the facter dosen't work. So that's not the
issue.
/Patrik
--
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 em
On 05/18/2011 05:18 PM, Patrick wrote:
>
> On May 18, 2011, at 1:20 AM, patant wrote:
>
>> Good idea!
>>
>>
>> Now I found another problem.
>> Some facts dosent't works when I call them explicit.
>>
>> The facter shows up in the list when I run facter --puppet.
>> But when I call facter --puppet
On May 18, 2011, at 1:20 AM, patant wrote:
> Good idea!
>
>
> Now I found another problem.
> Some facts dosent't works when I call them explicit.
>
> The facter shows up in the list when I run facter --puppet.
> But when I call facter --puppet it dosen't give me the value
> that I got in the
Good idea!
Now I found another problem.
Some facts dosent't works when I call them explicit.
The facter shows up in the list when I run facter --puppet.
But when I call facter --puppet it dosen't give me the value
that I got in the list. Returns nothing.
"facter" gives me:
--
uptime
Found the error:
require 'rubygems'
require 'mygem'
Facter.add("myfacter") do
setcode do
--
This works:
Facter.add("myfacter") do
require 'rubygems'
require 'mygem'
setcode do
---
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
T
I do require rubygems.
--
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
The gem is installed on the clients and the facter works on the client. It's
when I do the puppet apply/run I get the error.
--
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
