Hi,
Check this out:
https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html
It should provide you the info you are looking for...
Regards,
On Thursday, 3 March 2016 18:52:15 UTC, Matt Zagrabelny wrote:
>
> Greetings,
>
> I know that the puppet.conf documentation exists in
Odd, I don't see it there.
I'd expect something like:
runinterval = never
or something like that.
On Monday, November 25, 2013 11:10:49 AM UTC-8, Stuart Cracraft wrote:
Is there a way to prevent puppet from taking actions other than logging
using the puppet.conf file variables instead of
On Thu, Dec 29, 2011 at 4:01 PM, seanm reinvigor...@gmail.com wrote:
facter --version is showing: 1.5.7
It looks like there is have been quite a few ec2 fact improvements
since 1.5.7. The current version of facter is 1.6.4. You could try
that (download from apt.puppetlabs.com). I see five or
Thank you! $clientcert works like a charm!
I'm still unclear as to why I can't see any of the ec2 variables in my
ec2 instance. Is it because I'm running an old version of puppet or
something?
Sean
On Dec 29, 10:21 am, Nan Liu n...@puppetlabs.com wrote:
On Wed, Dec 28, 2011 at 7:38 PM, seanm
On Thu, Dec 29, 2011 at 10:59 AM, seanm reinvigor...@gmail.com wrote:
Thank you! $clientcert works like a charm!
I'm still unclear as to why I can't see any of the ec2 variables in my
ec2 instance. Is it because I'm running an old version of puppet or
something?
If you're running Puppet
facter --version is showing: 1.5.7
On Dec 29, 4:11 pm, Michael Stahnke stah...@puppetlabs.com wrote:
On Thu, Dec 29, 2011 at 10:59 AM, seanm reinvigor...@gmail.com wrote:
Thank you! $clientcert works like a charm!
I'm still unclear as to why I can't see any of the ec2 variables in my
Since I stumpled upon this bug I added the --no-client flag to the
puppet init script. Apart from being a bit ugly, it works fine.
It looks like this:
checkproc $puppetd --no-client --logdest /var/log/puppet/puppetd.log $
{PUPPET_OPTS} ${PUPPET_EXTRA_OPTS} touch ${lockfile}
I also added logdest
I've been fighting with this same issue in version 2.6.0. Setting client =
false in puppet.conf doesn't seem to do anything. Rather than modifying
the init script for puppet like Christian, I updated /etc/sysconfig/puppet
with the following line:
PUPPET_EXTRA_OPTS=--no-client
That's solved my
Phenomenal.. Thanks a lot guys.
Cheers,
On Sep 9, 8:45 am, M C maem...@gmail.com wrote:
I've been fighting with this same issue in version 2.6.0. Setting client =
false in puppet.conf doesn't seem to do anything. Rather than modifying
the init script for puppet like Christian, I updated
..
On Sep 7, 4:54 pm, CraftyTech hmmed...@gmail.com wrote:
Has anyone found a workaround for this? It appears that the bug
hasn't been fixed. I basically just need the daemon to run,
listening, without ever calling the puppetmaster on its own. My
clients are configured as follow:
Have you tried to set the interval to something very long and set the --noop
flag? (or what ever it's called) That should do something lose enough to what
you want that it won't matter.
On Sep 7, 2010, at 1:54 PM, CraftyTech wrote:
Has anyone found a workaround for this? It appears that the
The --no-client flag to puppetd didn't work for you? My understanding
of the bug is just that the client=false option isn't respected, but
if you specify it on the command line, it works fine. Right?
- Chad
On Tue, Sep 7, 2010 at 4:54 PM, CraftyTech hmmed...@gmail.com wrote:
Has anyone found
Has anyone found a workaround for this? It appears that the bug
hasn't been fixed. I basically just need the daemon to run,
listening, without ever calling the puppetmaster on its own. My
clients are configured as follow:
***
[puppetd]
report = true
listen = true
client
Gotcha.. thanks,
On Aug 3, 1:27 pm, Chad Huneycutt chad.huneyc...@gmail.com wrote:
There is a bug (http://projects.puppetlabs.com/issues/3313) about this.
On Tue, Aug 3, 2010 at 1:06 PM, CraftyTech hmmed...@gmail.com wrote:
Hello,
I have my clients' puppet.conf file setup as:
14 matches
Mail list logo
