Hi, On Sat, 2011-06-25 at 04:49 -0400, JP Vossen wrote:
On 06/24/2011 07:19 AM, Balazs Scheidler wrote:
On Mon, 2011-06-20 at 20:59 +0100, Jose Pedro Oliveira wrote:
There is a problem with the hash table implementation of glib2 version 2.12.3-4 (version that ships in RHEL 5.x). More details in:
Thanks for the information, if it's a glib bug then, can I help you in any way? Or I can "close" the issue?
I see that Jose already forwarded the bug, but I wonder; can you tell me what impact the failed test (and thus failed or potentially failed code block) may have on syslog-ng run-time on CentOS-5/RHEL5?
Is this hash problem going to cause critical failures? Under what circumstances? Or is it, well, it'd be nice if that hash problem didn't happen, but it's not a big deal...
Well, it probably mostly depends on why the hashtable collides in that glib version. This hash is a global hash that maps name-value pairs to their own unique IDs, which is then used to track name-value pairs in log messages. In case the hash table returns non-matching elements, it means that two (or more) different name-value pairs will map to the same id, effectively one overwriting the other. Whether it happens in practice actually depends on what the exact bug in glib is. -- Bazsi