Hi,
A question for the devs. Will this:
http://projects.puppetlabs.com/issues/4020
make it into a release any time soon?
Best regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
Sadly, signs point to no.
On Wed, Mar 2, 2011 at 5:15 AM, Martijn Grendelman mart...@iphion.nlwrote:
Hi,
A question for the devs. Will this:
http://projects.puppetlabs.com/issues/4020
make it into a release any time soon?
Best regards,
Martijn.
--
You received this message because
On 02-03-11 14:49, Brian Gallew wrote:
Sadly, signs point to no.
Too bad. But since I run a patched Puppetmaster anyway, I can do what I
want :-)
Unfortunately, it doesn't solve my problem.
I am trying to do the same thing as Gabriel Filion in this post:
Dude, I struggled with that for more than 6 months, and the position of the
Puppet people was, you're doing it wrong. Since that didn't help my problem
I ended up doing it this way:
1) Create a new fact (see attached) that reports back to the master server on
what classes are defined on the
Hello,
I finally abandoned the idea of having a group-based sane-looking Nagios
configuration with puppet, because there are too many weirdnesses in
Naginator. And unfortunately I can't really bring any help with patches
since I don't write any ruby..
There are some great nagios modules out
I've found that Puppet/Naginator has the bad habit of occasionally breaking the
Nagios config. Here's how I worked around this:
1) When you collect your Nagios resource, store them all in a temporary
directory (in my case, ~nagios/var/tmp)
2) Purge that directory with a cron job every night (so
On 03-03-11 08:04, Gabriel Filion wrote:
On 11-03-02 02:27 PM, Brian Gallew wrote:
I've found that Puppet/Naginator has the bad habit of occasionally
breaking the Nagios config. Here's how I worked around this: 1) When
you collect your Nagios resource, store them all in a temporary
directory
