From 79f8f9c199a30524b5636c00e86fc8f179caf6f2 Mon Sep 17 00:00:00 2001
From: Waldemar Brodkorb <mail@waldemar-brodkorb.de>
Date: Sat, 3 Dec 2011 12:21:37 +0100
Subject: add icinga core

---
 package/icinga/src/etc/icinga/resource.cfg | 32 ++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 package/icinga/src/etc/icinga/resource.cfg

(limited to 'package/icinga/src/etc/icinga/resource.cfg')

diff --git a/package/icinga/src/etc/icinga/resource.cfg b/package/icinga/src/etc/icinga/resource.cfg
new file mode 100644
index 000000000..d8f3e1473
--- /dev/null
+++ b/package/icinga/src/etc/icinga/resource.cfg
@@ -0,0 +1,32 @@
+###########################################################################
+#
+# RESOURCE.CFG - Sample Resource File for Icinga
+#
+# You can define $USERx$ macros in this file, which can in turn be used
+# in command definitions in your host config file(s).  $USERx$ macros are
+# useful for storing sensitive information such as usernames, passwords, 
+# etc.  They are also handy for specifying the path to plugins and 
+# event handlers - if you decide to move the plugins or event handlers to
+# a different directory in the future, you can just update one or two
+# $USERx$ macros, instead of modifying a lot of command definitions.
+#
+# The CGIs will not attempt to read the contents of resource files, so
+# you can set restrictive permissions (600 or 660) on them.
+#
+# Icinga supports up to 32 $USERx$ macros ($USER1$ through $USER32$)
+#
+# Resource files may also be used to store configuration directives for
+# external data sources like MySQL...
+#
+###########################################################################
+
+# Sets $USER1$ to be the path to the plugins
+$USER1$=/usr/libexec
+
+# Sets $USER2$ to be the path to event handlers
+#$USER2$=/usr/libexec/eventhandlers
+
+# Store some usernames and passwords (hidden from the CGIs)
+#$USER3$=someuser
+#$USER4$=somepassword
+
-- 
cgit v1.2.3