From b74ea32070492c251943d69a09265463cc9866ed Mon Sep 17 00:00:00 2001
From: "Suren A. Chilingaryan" <csa@suren.me>
Date: Wed, 4 Sep 2019 22:54:49 +0200
Subject: Cleaned configuration for PDV infrastructure (incomplete) integrated
 with my Conky monitoring scripts

---
 config/new/resource.cfg | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 config/new/resource.cfg

(limited to 'config/new/resource.cfg')

diff --git a/config/new/resource.cfg b/config/new/resource.cfg
new file mode 100644
index 0000000..b26de4f
--- /dev/null
+++ b/config/new/resource.cfg
@@ -0,0 +1,33 @@
+###########################################################################
+#
+# RESOURCE.CFG - Sample Resource File for Nagios 4.4.4
+#
+#
+# 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.
+#
+# Nagios supports up to 256 $USERx$ macros ($USER1$ through $USER256$)
+#
+# 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$=/opt/nagios/libexec
+
+# Sets $USER2$ to be the path to event handlers
+#$USER2$=/opt/nagios/libexec/eventhandlers
+
+# Store some usernames and passwords (hidden from the CGIs)
+#$USER3$=someuser
+#$USER4$=somepassword
+
-- 
cgit v1.2.3