On Mon, 22 Apr 2013 10:08:45 +0200
Dirk Heinrichs wrote:
> On Mon, Apr 22, 2013 at 12:45:35AM -0700, Paul Tötterman wrote:
>
> > Shouldn't environment variables be case-insensitive? What code is
> > responsible for expanding those environment variables?
>
> This is Windows, so I'd say: "It dep
On Mon, Apr 22, 2013 at 12:45:35AM -0700, Paul Tötterman wrote:
> Shouldn't environment variables be case-insensitive? What code is
> responsible for expanding those environment variables?
This is Windows, so I'd say: "It depends". I can do this:
C:\Program Files (x86)\Puppet Labs\Puppet\bin>ec
>
> Found it: The two occurrences of %SystemRoot% should really be
%SYSTEMROOT%. Fixed it, works now.
>
Shouldn't environment variables be case-insensitive? What code is
responsible for expanding those environment variables?
Cheers,
Paul
--
You received this message because you are subscr
On Mon, Apr 22, 2013 at 08:58:31AM +0200, Dirk Heinrichs wrote:
> C:\Program Files (x86)\Puppet Labs\Puppet\bin>facter path
> C:\Program Files (x86)\Puppet Labs\Puppet\puppet\bin;C:\Program Files
> (x86)\Puppet Labs\Puppet\facter\bin;C:\Program Files (x86)\Puppet
> Labs\Puppet\hiera\bin;C:\Progr
On Sat, Apr 20, 2013 at 01:55:46PM +0200, Stefan Schulte wrote:
> We'll first try to get a clearer error message. Please go to your facter
> installation directory on your agent and modify the file
> `util/resolution.rb`. Change
>
> Facter.warnonce 'Using Facter::Util::Resolution.exec with a shel
On Tue, 16 Apr 2013 22:46:53 -0700 (PDT)
Larry Fast wrote:
>
> Side issue: diagnostics could have been better. The error did not
> indicate a source file. And Pluginsync does not indicate the source
> module for any of the files it loads. Not even in debug mode.
>
FYI: I created a feature req
On Fri, 19 Apr 2013 13:50:59 +0200
Dirk Heinrichs wrote:
> I'm facing a similar problem, on one single Windows machine out of
> more than 100. If I run any puppet command, I get above warning.
We'll first try to get a clearer error message. Please go to your facter
installation directory on your
On Fri, Apr 12, 2013 at 12:23:45PM -0700, Larry Fast wrote:
> Windows NuBQ:
> I'm running windows with a clean install of puppet and an empty node
> definition. puppet agent -t pauses with no prompt. When I hit enter, I
> get this warning:
>
> Using Facter::Util::Resolution.exec with a shell
Solution:
Find the .rb files that contained Facter::Util::Resolution.exec and ...
Facter.add("my_function") do
confine :kernel => [ 'Linux' , 'SunOS' , 'FreeBSD' , 'Darwin' ]
...
Thanks everyone!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" g
On 04/17/2013 07:46 AM, Larry Fast wrote:
> I think I found the problem. Pluginsync seems to load ALL plugins -
> even for modules that are not included in that node's manifest. Is this
> correct?
Yes. Pluginsync happens before the manifest is even compiled. This is a
logical necessity. E.g. you
I think I found the problem. Pluginsync seems to load ALL plugins - even
for modules that are not included in that node's manifest. Is this correct?
I think my problem is a plugin that runs fine in Unix but does not work
properly in windows.
Side issue: diagnostics could have been better.
On Saturday, April 13, 2013, Paul Tötterman wrote:
> Hi,
>
> How do I fix/disable this warning?
>>
>
> It seems like you've added some extra facter facts? They seem to be
> implemented incorrectly. Remove the problematic one.
>
> Cheers,
> Paul
>
> --
> You received this message because you are su
Windows NuBQ:
I'm running windows with a clean install of puppet and an empty node
definition. puppet agent -t pauses with no prompt. When I hit enter, I
get this warning:
Using Facter::Util::Resolution.exec with a shell built-in is deprecated.
Most built-ins can be replaced with native ruby
13 matches
Mail list logo
