Hi Antony,
> - rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist (it
> doesn't really matter what, just change its name)
>
> - create a new, empty /etc/icinga2/conf.d and leave it empty
... or, much more straightforward:
- comment the line saying 'include_recursive "conf.
On Thursday 22 December 2016 at 10:36:37, Peter Eckel wrote:
> Hi Antony,
>
> > - rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist
> > (it doesn't really matter what, just change its name)
> >
> > - create a new, empty /etc/icinga2/conf.d and leave it empty
>
> ... or, much
Am 06.10.2016 um 00:05 schrieb Barry Quiel:
Hi Barry,
sorry for the late reply. I got the same problem and solved it finally.
> So I was going to go on a long diatribe about the necessity for
> dependencies across zones, but I found, really by accident, that most
> of what I was looking for was
Dear All ,
I am broseth . I want to install icinga2 for monitor my server and network
device.
Could u give me the documentary ?
Regards
Broseth
-Original Message-
From: icinga-users [mailto:icinga-users-boun...@lists.icinga.org] On Behalf
Of Antony Stone
Sent: Thursday, December 22, 2016
Hi @ll,
I strongly opt for Peters approach, that's in fact how I configure all
my systems. The problem with conf.d is that it contains files provided
by upstream. Depending on your package manager the next upgrade might
re-create files you formerly deleted - and you're doomed.
Most package manage
On Thursday 22 December 2016 at 10:54:59, broseth wrote:
> Dear All ,
>
> I am broseth . I want to install icinga2 for monitor my server and network
> device.
Please start a new thread if you wish to discuss a new topic.
> Could u give me the documentary ?
https://docs.icinga.com/icinga2/lates
