Displaying 5 results from an estimated 5 matches for "puppet_conf".
2007 Aug 22
6
Re: [puppet] #779: access to inherited variables from within a template
puppet schrieb:
> #779: access to inherited variables from within a template
> -----------------------------------------+----------------------------------
> Reporter: simu | Owner: luke
> Type: enhancement | Status: new
> Priority: normal | Milestone:
>
2010 Jun 28
4
Error 400 : could not find template
.....
Jun 28 09:46:17 tsta puppetd[31413]: Could not retrieve catalog from
remote server: Error 400 on SERVER: Could not find template
''etc/motd.erb'' at /etc/puppet/manifests/classes/motd.pp:6 on node
tsta.....
This is the class to serve the puppet.conf file:
class puppet {
$puppet_config_dir = "/etc/puppet/"
$puppet_conf = "$puppet_config_dir/puppet.conf"
user {
"puppet":
ensure => present;
}
file {
$puppet_config_dir:
ensure => directory,
ow...
2011 Jun 27
12
Ruby script to download files without 'puppet agent'
We have often the Problem that some files need to be checked for updates
faster than the cycle of the puppet agent. I try to solve this with a
script which tries to download the files directly from the fileserver of
the puppetmaster. So far i couldn''t get it to work.
I don''t know if i got the URL right, i did not find any examples on the
REST API documentation for the
2013 Feb 01
11
Change the location of puppet.conf
...cation of puppet.conf? In my
situation, I don''t want to store it under /etc/puppet/puppet.conf or
~/.puppet/puppet.conf -- I''d like to store it under /opt/puppet/puppet.conf
in this example. Is there a method without having to symlink, perhaps with
an environment variable like PUPPET_CONF=.... ?
Thanks for your time,
Jason
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To post to this group, se...
2011 Sep 23
21
Official puppetlabs position on cron vs puppet as a service?
Over the years many shops have come to start running puppet via cron to
address memory leaks in earlier versions of Ruby, but the official position
was that puppet was meant to be run as a continually running service.
I am wondering if the official position has changed. On one hand many if not
all of the early Ruby issues have been fixed, on the other, the addition of
mcollective into the mix as