From 764740bd305e9eb823bf05b855d51c0d9c6f0af0 Mon Sep 17 00:00:00 2001 From: mh Date: Fri, 25 Apr 2008 17:04:34 +0000 Subject: moved dir --- files/configs/private/resource.cfg.x86_64 | 34 +++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 files/configs/private/resource.cfg.x86_64 (limited to 'files/configs/private/resource.cfg.x86_64') diff --git a/files/configs/private/resource.cfg.x86_64 b/files/configs/private/resource.cfg.x86_64 new file mode 100644 index 0000000..b9f0841 --- /dev/null +++ b/files/configs/private/resource.cfg.x86_64 @@ -0,0 +1,34 @@ +########################################################################### +# +# RESOURCE.CFG - Sample Resource File for Nagios 2.9 +# +# Last Modified: 09-10-2003 +# +# 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 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/lib64/nagios/plugins + +# Sets $USER2$ to be the path to event handlers +#$USER2$=/usr/lib64/nagios/plugins/eventhandlers + +# Store some usernames and passwords (hidden from the CGIs) +#$USER3$=someuser +#$USER4$=somepassword + -- cgit v1.2.3