availability report has too much "indeterminate"

[Philip Brown]

On Wed, Feb 26, 2003 at 03:06:23PM +1100, Stanley Hopcroft wrote:
> Dear Sir,
> 
> Does this help,
> 
> http://www.nagios.org/faqs/viewfaq.php?faq_id=136

Thank you for replying. However, no, it does not help.
It sugests some hacks and workarounds, like setting 
"assume state retention", and increasing "Backtracked Archives" count.

This is not reasonable behaviour. The demon should take care of this sort
of thing for the user automatically. This should be considered a bug.

May I suggest two fixes for this issue that work together:

1. If the demon has been HUPped, it should be considered a non-event,
   as far as the historical "service available" data goes
  (unless of course the service has just been configured in that reload)

2. The demon stores the state of every single service, at the start of
   each new archive log rotation.
   This will categorically remove any ambiguity about previous state, and
   remove the need for the hack that is archive "backtracking".



-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
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