author | Andrés J. Díaz <ajdiaz@connectical.com> | |
Wed, 27 May 2009 09:14:40 +0000 (11:14 +0200) | ||
committer | Florian Forster <octo@huhu.verplant.org> | |
Wed, 27 May 2009 09:16:34 +0000 (11:16 +0200) | ||
commit | a2463af54cf007072aa433c5c1833958ca6050df | |
tree | 05cb8a5c678c31876d48d2bdb34376701f6a5db6 | tree | snapshot |
parent | 799daf946e48c5c3b5f6b016bc9290fe562f062d | commit | diff |
src/utils_cache.c: Fix incorrect checking of persistent thresholds.
I attached a patch to solve a problem related with notifications. When a value
is missing for a while (2 intervals), a FAILURE notification is raised, and if
Persist is false, the notification is repeated each interval, but man page
says:
If set to false (the default) then a notification is only generated if a
value is out of range but the previous value was okay.
So, I think that is a bug, if not I'm sorry for the noise :)
Regards,
Andres
P.S.: The problem is only a mixing in if conditions into uc_check_timeout
function.
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
I attached a patch to solve a problem related with notifications. When a value
is missing for a while (2 intervals), a FAILURE notification is raised, and if
Persist is false, the notification is repeated each interval, but man page
says:
If set to false (the default) then a notification is only generated if a
value is out of range but the previous value was okay.
So, I think that is a bug, if not I'm sorry for the noise :)
Regards,
Andres
P.S.: The problem is only a mixing in if conditions into uc_check_timeout
function.
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
src/utils_cache.c | diff | blob | history |