Bug fix priority

[Julien Mathis]

Hello All

I am increasingly surprised at the enthusiasm that can cause scheduling bug
(2010 problem) and bug 57 (http://tracker.nagios.org/view.php?id=57).

It is rather problematic to see a scheduler doing a break until 2010 at the
same date that the next check because we do not monitor 24/24 7/7 ... If we
do not have eyes on the screen, we are not warned ... less well to do even
on a patch-based cron.

Nobody is impacted by this problem? I see a lot of minor bugs on the mailing
list and I think this bug have the most impact. If a scheduler stop to
schedule, it loses some of its interest ... And more over, it loses
credibility.

This is a bug which is known since several months, and I just think it
should be fixed in urgence. I know we tried to solve a short time ago
without success.

What do you think about that ?

Regards,
--
 Julien MATHIS | CTO

jmathis at merethis.com

MERETHIS is editor of Centreon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20090807/92999495/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- next part --------------
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel