Thanks for the info. So for example, it wants me to define new hosts in the
windows.cfg. Is there a point to that? Can I just put service definitions
in the windows.cfg and utilize the hosts I already have defined in hosts.cfg
?
On 6/26/07, Frost, Mark {PBG} <[EMAIL PROTECTED]> wrote:
Jerad,
I took this to mean that it's a sort of generic/example config file. You
can always break out your configuration into additional files/directories as
makes sense for your installation as long as you add new lines in the
nagios.cfg file to tell it to read each new file and/or directory you
create.
I found that a few things in that 3.0 doc for monitoring with NSClient++
that weren't correct so you will find yourself making some modifications to
get things to work if you've completely copied entries from that doc page.
Mark
------------------------------
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Jerad Riggin
*Sent:* Tuesday, June 26, 2007 9:16 AM
*To:* nagios-users@lists.sourceforge.net
*Subject:* [Nagios-users] Windows monitoring
I'm going through this article:
http://nagios.sourceforge.net/docs/3_0/monitoring-windows.html
It is referring to a windows.cfg within nagios.cfg. I don't see any such
commented out line in my nagios.cfg, and I can't even find a windows.cfgat all.
Is the difference that I am running
2.9 and this is referring to 3.0?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
