-----Ursprüngliche Nachricht-----
Von: icinga-users [mailto:[email protected]] Im Auftrag von
[email protected]
Gesendet: Sonntag, 31. Januar 2016 12:00
An: [email protected]
Betreff: icinga-users Digest, Vol 25, Issue 44
Send icinga-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.icinga.org/mailman/listinfo/icinga-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of icinga-users digest..."
Today's Topics:
1. Proper way to init global-zones in distributed zone setup
(Henriette)
2. Re: e-book version (epub, pdf, ...) from the documentation
(Henriette)
3. Wrong link in Icinga2 docs -- NagVis (Henriette)
----------------------------------------------------------------------
Message: 1
Date: Sat, 30 Jan 2016 20:34:46 -0800
From: Henriette <[email protected]>
To: [email protected]
Subject: [icinga-users] Proper way to init global-zones in distributed
zone setup
Message-ID: <20160130203446.2133e127@Secure>
Content-Type: text/plain; charset=US-ASCII
Hello,
I have a distributed zone setup and besides the satellite/master zones on the
parent I have a global-template zone that I want to share. (global="true" is
set in zones.conf on parent)
Now when I configure a new satellite via icinga2 node wizard, the satellite
will receive by default only the config of its zone and say in the log:
"warning/ApiListener: Ignoring config update for unknown zone
'global-template'."
Of course I could make the global-template zone known to the satellite simply
by editing zones.conf on the satellite by hand, after having it set up. But I
was wondering if there is another more easy way.
What is the workflow here with which the feature "global-flag" feature was
implemented?
Best Henriette
------------------------------
Message: 2
Date: Sat, 30 Jan 2016 21:50:06 -0800
From: Henriette <[email protected]>
To: <[email protected]>
Subject: Re: [icinga-users] e-book version (epub, pdf, ...) from the
documentation
Message-ID: <20160130215006.4ee702a7@Secure>
Content-Type: text/plain; charset="us-ascii"
Hello Jean-Marcel,
when I just tried to follow your advice I noticed two things.
First the url to the actual repository is just for convenience:
git://git.icinga.org/icinga2.git
or
http://git.icinga.org/icinga2.git
Second there were several not properly escaped sequences in
doc/7-icinga-template-library.md
Namely it were the backslashes in front of \n, \r, \t, see the patch in the
appendix.
For convenience again, after applying the patch one could then get a pdf manual
on *nix systems through:
git clone http://git.icinga.org/icinga2.git icinga2 cd icinga2/doc pandoc --toc
--latex-engine=xelatex -o Manual.pdf 1-about.md \ 2-getting-started.md
3-monitoring-basics.md 4-configuring-icinga-2.md \ 5-advanced-topics.md
6-object-types.md 7-icinga-template-library.md \ 8-cli-commands.md
9-icinga2-api.md 10-monitoring-remote-systems.md \ 11-icinga2-client.md
12-agent-based-checks.md 13-distributed-monitoring-ha.md \ 14-addons-plugins.md
15-features.md 16-troubleshooting.md \ 17-upgrading-icinga-2.md
18-language-reference.md 19-library-reference.md \ 20-script-debugger.md
21-development.md 22-migrating-from-icinga-1x.md \ 23-appendix.md
supposing latex2pdf and pandoc are installed and properly set up.
Best
Henriette
>
Thanks, I'll try that. If that's so easy maybe you could include the process of
creating pdf and/or epubs with every new documentation release?
Greetings and thanks,
Tobias
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
