-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15/02/09 09:29 PM, Sean Carolan wrote:
>> The only way would be modifying the CGI code. Be aware though that the
>> CGI interface will be replaces by a PHP one in the next major release..
>>
> 
> Very interesting.  I just asked because we like to see "all green" on
> the control panel, makes it easy to identify a problem when the normal
> state is all green.

There has been a similar question asked on the devel mailing list - you
should have a look (see attached).

> Will the new PHP version have a clear upgrade path from 3.0.4?

Most likely like the other upgrades which usually required little or no
extra setup. Right now I think it requires NDODB, but I hope it will
have a plain-file based alternative (I will try to suggest CDB as a
backend replacement for the plain text status files) as NDODB pushes the
complexity level a notch higher IMHO.

- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJmRPt6dZ+Kt5BchYRApYdAJ0XgYJvm6MC5bcbivr4wIuQgxp4EQCg8QuD
NKRDMKFOcJsCfMKgsb+RJgo=
=wB3O
-----END PGP SIGNATURE-----
--- Begin Message ---
Hi'

For passive only services I would like to use option

check_period   none

instead of option
  
active_checks_enabled   0

since the latter gives rise to showing these checks as disabled in the
"tactical overview", which the former does not. It is less confusing
for our operators to not see anything being disabled.

Now I have spiced these passive only checks up with freshness checkings, see 
docs/freshness.html, but it seems, that this only works, if I use 
"active_checks_enabled 0" instead of "check_period none". One might suspect 
that, but docs/timeperiods.html states, that "Note: On-demand checks and 
passive checks are not restricted by the timeperiod you specify in the 
check_period directive. Only regularly scheduled active checks are 
restricted.". Would you think, that freshness checking should also fall under 
that category.

Also, the FAQ at 
http://www.nagios.org/faqs/viewfaq.php?faq_id=271&expand=false&showdesc=false 
seems to indicate, that using "check_period none" would be the right thing to 
do, but maybe that was true only in an earlier release.

Best regards.

Thomas.


      ________________________________________________________ 
Audi, Fiat, Peugeot, Skoda, Porsche, Toyota, Ford - Kelkoo har brugte biler til 
en hver smag! Klik her for at sammenligne priser.(http://dk.yahoo.com/r/pat/mmb)
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Nagios-devel mailing list
nagios-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13/02/09 08:45 AM, Thomas Lorenzen wrote:
> Hi'
> 
> For passive only services I would like to use option
> 
> check_period   none
> 
> instead of option
>  
> active_checks_enabled   0
> 
> since the latter gives rise to showing these checks as disabled in the
> "tactical overview", which the former does not. It is less confusing
> for our operators to not see anything being disabled.
> 
> Now I have spiced these passive only checks up with freshness checkings,
> see docs/freshness.html, but it seems, that this only works, if I use
> "active_checks_enabled 0" instead of "check_period none". One might
> suspect that, but docs/timeperiods.html states, that "Note: On-demand
> checks and passive checks are not restricted by the timeperiod you
> specify in the check_period directive. Only regularly scheduled active
> checks are restricted.". Would you think, that freshness checking should
> also fall under that category.
> 
> Also, the FAQ at
> http://www.nagios.org/faqs/viewfaq.php?faq_id=271&expand=false&showdesc=false
> seems to indicate, that using "check_period none" would be the right
> thing to do, but maybe that was true only in an earlier release.

You can try the patch attached, although I doubt Ethan will accept it.
He's the one who "Fixed" freshness checks running despite of timeperiod
in 2004:

commit eeb5ca93945994826afc921dc99c650bf5a3fc48
Author: Ethan Galstad <egals...@nagios.org>
Date:   Thu Jun 24 05:03:29 2004 +0000

    Freshness checking timeperiod bug fix

OTOH many people complain about passive services showing as "Disabled"
in the tactical overview.

Another fix would be not to show them as disabled in the CGI if the
following conditions are true (any of them will prevent freshness checks
from running):
  - Freshness checking is enabled globally
  - Freshness checking is enabled on the service
  - Passive checks are enabled
  - Either check_interval or freshness interval is defined

I can do that if it's going into mainline.

- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJlvij6dZ+Kt5BchYRAqMYAKDGB/Mqmhi9/YnlxhKuX2FUUHCIygCg0B0o
wGO5gKP+liVnBmiuH0ykY2U=
=LJ/9
-----END PGP SIGNATURE-----
diff --git a/base/checks.c b/base/checks.c
index 9d5c497..4d0f427 100644
--- a/base/checks.c
+++ b/base/checks.c
@@ -1978,9 +1978,9 @@ void check_service_result_freshness(void){
 		if(temp_service->is_being_freshened==TRUE)
 			continue;
 
-		/* see if the time is right... */
+		/* see if the time is right... FIX: According to faq_id=271 we shouldn't.
 		if(check_time_against_period(current_time,temp_service->check_period_ptr)==ERROR)
-			continue;
+			continue; */
 
 		/* EXCEPTION */
 		/* don't check freshness of services without regular check intervals if we're using auto-freshness threshold */
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Nagios-devel mailing list
nagios-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel

--- End Message ---
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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

Reply via email to