Hello
I often configure a new node that I want to be the same as an existing one.
However I'd like to run puppetd with --noop just the once to double
check the changes (I'm still responsible for them after all)
Trouble is on a new node the keys etc aren't there and running as noop
they don't get
next if FileTest.directory?(report)
> thisreport = open(report) { |fh| YAML::load(fh) }
> print "Host: " + thisreport.host
> reporttime = File.stat(report).mtime.to_i # seconds since epoch...
> thisreport.logs.each do |log|
> # Whatever you want to find out abo
Evening All,
I've been getting a random number of copies of report mails, the same
report sent multiple times at the same second, and finally got tired
enough of it to look into it.
They are sent from puppet rather than a mail server issue.
I get one extra copy every time the client gets a "wa
Hello
If you really want all disks 2000 then net-snmp's "includeAllDisks 2000"
might do for you.
Neil
Xavier Beaudouin wrote:
> Hello there,
>
> I would like to automatize my snmpd.conf with all local disks discovered
> by puppet.
>
> For example, in my template : snmpd.erb I have :
>
> --//-
off the top of my head try quoting the package name
package { "admin-users": ensure => latest }
Neil
dj wrote:
> I'm trying to build a minimal class that installs a package on a
> centos machine.
>
> here is the class:
>
> class admin-users {
>
> package { admin-users: ensure => latest }
>
>
RPM
> provided puppet.conf file.)
>
> Tools designed to make a system administrator's life easier shouldn't
> cause such confusion... :)
>
> Neil Prockter wrote:
>> puppetd.conf is no more, use puppet.conf
>>
>> Many people have had the same confusing situa
jcbollinger wrote:
>
>
> On Sep 17, 2:53 pm, David Sowder wrote:
>> I'm in the process of upgrading a bunch of our Puppet clients from 0.22.4 to
>> 0.24.8 after recently upgrading our puppetmaster similarly.
>>
>> I've run into a problem that seems like it'd be so likely seen by someone
>> el
puppetd.conf is no more, use puppet.conf
Many people have had the same confusing situation with --noop being
similarly ignored.
Neil
David Sowder wrote:
> I'm in the process of upgrading a bunch of our Puppet clients from 0.22.4 to
> 0.24.8 after recently upgrading our puppetmaster similarly.
>
