Active/Passive bug?

[Alan Maxwell]

I've always liked the fact that Nagios is very flexible in many areas,
but this particular scenario I consider a bug:
 
I have a check that I want to be passive, the check_command portion is
set to simply exit with the appropiate code.
 
But in the GUI, a user can select this service, then "enable active
checks of this service"
This then caused me big problem, that the service showing warnings then
was not actually in warning but was
forced to execute the check_command.
 
In my mind there ought to be a more strict parameter for a check, an
actual "check_type"
You could have active, passive, both.
 
But then if a check is clearly defined as active, then never allow the
web/cgi to then "enable passive checks".
 
 
 
Bottom line, I see this as an error , allowing the web interface to
enable checks , that are not desired to run.
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060724/0bf27860/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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