--0016363b96d4c06c1d04708d7973
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
[email protected]
MERETHIS is editor of Centreon.
--0016363b96d4c06c1d04708d7973
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Hello AllI 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 | [email protected]
MERETHIS is editor of Centreon.
--0016363b96d4c06c1d04708d7973--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]