-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ricardo Maraschini schrieb:
> Hi,
>
> ----- "Ricardo Maraschini" escreveu:
>> get_next_valid_time(preferred_time,&next_valid_time,svc->check_period_ptr);
>>
>> as
>>
>> get_next_valid_time(current_time,&next_valid_time,svc->check_period_ptr);
>>
>>
>> The problem occurs when preferred_time( that is current_time +
>> svc->check_interval in case of error on call run_async_service_check)
>> is inside timeperiod configuration.
Are you shure that the problem hits us, when the calculation is 'inside'
a timeperiod?
I thought it leads into false calculation when prefered_time results
outside a timeperiod like it is within a exluded tp.
>
> So, who is the responsable for Nagios right now?
Ethan Galstad (Contacts on nagios.org) or better on this list.
> Why we aren't discussing the bug?
Since atm nagios seems to be a one-man-show, may be he's not available
at the moment.
> We must stay in this vacuum every time a patch/bug is submited/reported?
>
No we must not. Just send a unified diff against the latest cvs code to
this list and other people might review it.
Since this is a very strange problem a "how to come to this bug"
description would be usefull too.
Something like:
Take a timeperiod configuration which exlude the next hour from now
Use this tp as a check_period for a single service and look at the
calculated times.
Regards,
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAknUU+IACgkQlI0PwfxLQjkgdwCfTwNQ+0rQNZnXR9m29x/frQKr
s50AnivGm6WuJqe+vmRUMFAIJRjXZYLt
=jUjc
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]