Hi all,
Sorry to not reply earlier.
All you mention work fine. The directory can be change using the target
parameter. The path must be absolute.
Thanks for all.
Juan-FRancisco
2011/4/29 lluis
> Hi,
> beware of this if you change default file locations:
>
> "You can purge Nagios resources us
Hi,
beware of this if you change default file locations:
"You can purge Nagios resources using the resources type, but only in
the default file locations. This is an architectural limitation"
on Debian I prefer to link /etc/nagios3/conf.d to /etc/nagios
greetings,
Lluís
El dt 26 de 04 de 2011 a
Hello,
On 11-04-26 05:48 AM, Juan-Francisco Diez wrote:
> OK, thenks for your help. I solved the trouble using the $hostname fact
> in front of services definitions.
>
> But I have another question about this:
>
> Is it possible to define the directory where the file are created in the
> nagios
Hello again,
Yes, of course you can change the directory.
Check out the mentioned module, we put all the nagios stuff in /etc/nagios.d
directory, keeping clean a /etc/nagios3 directory. For what I've seen, it seems
to do exactly what you're trying to do.
For the basic:
nagios accept different
OK, thenks for your help. I solved the trouble using the $hostname fact in
front of services definitions.
But I have another question about this:
Is it possible to define the directory where the file are created in the
nagios server?
Now the files are stored in the /etc/nagios.
2011/4/26 Cedri
Hello,
Maybe have a look at our nagios module:
https://github.com/camptocamp/puppet-nagios
Your problem is that resources with same name are exported from multiple hosts,
and that make puppet crash with duplicated definition (as it's exported
resources, the error message is different ;) ).
You
Hi everyone,
I'm trying to automate the nagios configuration of new host through
Puppet. For this I define a nagios module with the generic
configuration of my Nagios host definition. The module look like
this:
class nagios {
$packagelist=["nagios"]
package { $packagelist:
