<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: [Nagios-users] defining passive services</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Use whatever check command you like. Check_dummy or check_ping might be a good one. As long as you either have active_checks_enabled set to 0 or the check_period set to none, it'll never get executed. It does need to match a valid command definition though. The preferred way of doing it would be to create a comand definition that somwhat resembles the check you are doing but that's mostly for human readability, IMHO.<BR>
<BR>
<BR>
<BR>
<BR>
--<BR>
Marc<BR>
<BR>
-----Original Message-----<BR>
From: Peter Hicks <petong@jah.net><BR>
To: nagios-users@lists.sourceforge.net <nagios-users@lists.sourceforge.net><BR>
Sent: Fri Oct 03 17:52:56 2003<BR>
Subject: [Nagios-users] defining passive services<BR>
<BR>
Hello all,<BR>
<BR>
I have a question regarding the configuration of passive alerts. I have<BR>
nsca set up to receive alerts from lrrd, and this seems to be working<BR>
fine. It appears that nsca is passing these alerts on to nagios. My<BR>
question is how to properly define a service to accept these passive<BR>
alerts.<BR>
<BR>
The service in question that I am monitoring is cpu usage. When<BR>
cpu usage exceeds 90%, an alert is sent out. I have<BR>
passive_checks_enabled in service.cfg, but each service definition needs<BR>
a check_command by default.<BR>
<BR>
What do I need to do to get this last bit working?<BR>
<BR>
Thanks!<BR>
<BR>
-Peter<BR>
<BR>
<BR>
-------------------------------------------------------<BR>
This sf.net email is sponsored by:ThinkGeek<BR>
Welcome to geek heaven.<BR>
<A HREF="http://thinkgeek.com/sf">http://thinkgeek.com/sf</A><BR>
_______________________________________________<BR>
Nagios-users mailing list<BR>
Nagios-users@lists.sourceforge.net<BR>
<A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A><BR>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<BR>
::: Messages without supporting info will risk being sent to /dev/null<BR>
</FONT>
</P>
</BODY>
</HTML>