t; privileges.
Deleting the folder structure under c:\ProgramData\PuppetLabs and then
re-running with the correct privileges has solved the CPU issue.
Matt
On Thu, Mar 8, 2012 at 10:47 AM, Josh Cooper wrote:
> HI Matt,
>
> On Thu, Mar 8, 2012 at 6:45 AM, Matt Mencel wrote:
>
>>
I recently noticed that the Windows host where I installed the Puppet agent
for testing was thrashing the CPU.
The culprit ended up being Ruby.exe *32 - "Ruby interpreter (CUI) 1.8.7.334
[i386-mingw32]". This is actually being launched by the puppet-agent
service in Windows. The CPU on the host
Thanks to both of you... :)
Matt
--
*From: *"Peter Bukowinski"
*To: *puppet-users@googlegroups.com
*Sent: *Wednesday, February 29, 2012 1:01:14 PM
*Subject: *Re: [Puppet Users] Modifying a FACT Value In a Manifest
On Feb 29, 2012, at 1:10 PM, Matt Mencel
In my network every subnets default gateway is X.X.X.1. That router
gateway is always running ntpd which I want to give be default as the ntp
server in every hosts ntp.conf.
Since there is no official "default gateway" fact yet, what I want to be
able to do in my manifest is take the $ipaddress f
I'm curious about the section "Caching Ruby Facts" on this doc page...
http://docs.puppetlabs.com/guides/custom_facts.html#configuring-facts
Apparently this ability to assign a TTL value to a fact will be in place in
1.7.0. I've looked through the Facter source and wiki though and find no
mention
Awesomethank you!
On Tue, Feb 21, 2012 at 10:48 AM, jcbollinger wrote:
>
>
> On Feb 21, 9:21 am, Matt Mencel wrote:
>
> > The only examples I've seen of timeout have it outside the setcode block.
> > Can anyone confirm it's behavior depending on whether
> On Feb 20, 7:14 pm, Nathan Powell wrote:
> > On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel wrote:
> > > I am trying to write a custom facter for CentOS/RHEL that tells me how
> many
> > > updates are found on a run of 'yum check-update'
> >
>
Hi Nathan,
Excellent! Thanks for the tip.
Matt
On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel wrote:
> I am trying to write a custom facter for CentOS/RHEL that tells me how
many
> updates are found on a run of 'yum check-update'
Sorry I replied hastily. After replying I th
I am trying to write a custom facter for CentOS/RHEL that tells me how many
updates are found on a run of 'yum check-update'
Facter.add(:cis_yum_check) do
timeout = 300
setcode do
File.open("/tmp/yum_check-update", 'w') { |f| f.write(`/usr/bin/yum
check-update`) }
back_arr = []
f =
