search for: guardiannew

Hi All, I was wondering if it is possible to NOT show an event in puppet dashboard. I have an exec resource that fires of a ruby script. This is triggering a changed event on every run, but actually I want to exclude this from showing up as "CHANGED" Is this possible, if so how can I achieve this? --- myscript: --- exec { "run_myscript" : #

Hello list. I''ve the following parent class: class munin::client { ... munin::client::plugin { "postfix_mailqueue": name => "postfix_mailqueue", enable => "false" } } And the following inherited class: class munin::client::plugins::postfix inherits munin::client { munin::client::plugin {

I have tried to use config_version and failed due to limitations in the way I would like to use it: - http://projects.puppetlabs.com/issues/3692 - http://projects.puppetlabs.com/issues/4845 - http://projects.puppetlabs.com/issues/5404 As part of http://projects.puppetlabs.com/issues/3692, we''d like to get a handle on who in the puppet community is using config_version successfully as it

Here''s one for you! We''re rolling out some zip files to our servers using Puppet, there''s an exec that unzips them, the zip file is then deleted. I need to remove the old versions of the unzipped directory using Puppet when we rol out a newer version. So, on my client/node machine I have the below directories. /opt/1234 /opt/12345 /opt/123456 What I need to do, is

I''m running puppet on a Centos 5.8 I''m trying to launch puppet as a daemon and it fail silently. --debug provides no help So I tried to strace it, I''m getting this : 1845 close(0) = 0 1845 open("/dev/null", O_RDONLY) = 0 1845 close(1) = 0 1845 open("/dev/null", O_WRONLY|O_CREAT|O_APPEND,