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 more straightforward:
>
> - comment the line saying 'include_recursive "conf.d"' at the end of
> /etc/icinga2.conf
>
> so there isn'a a mythical directory in the hierarchy that needs to be kept
> empty. Things like that WILL backfire sooner or later when you don't
> expect it.
Yes, you can do this, however on the other hand that leaves a directory
/etc/icinga2/conf.d with lots of useful-looking files in it, which could be
tempting to edit and add content to, without it being obvious that Icinga
isn't even looking there any more :)
I think your solution is just as good as mine - so long as you remember what
you've done.
Anyone else coming along to look at the system might start using that
directory (empty in my case, not in yours) and get confused :(
Antony.
--
"I estimate there's a world market for about five computers."
- Thomas J Watson, Chairman of IBM
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
