-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 18 Jan 2009 12:01:53 +0100 Rainer Gerhards <[email protected]> wrote:
> From what I have seen so far, I, too, doubt there is a leak. However, > there are various levels of testing. For example, the postgres output > module and the GSSAPI code is contributed and I do not even have a > test environment. So these are not checked using that procedure. The > libdbi code is only checked every now and then and not with all > backends (e.g. no Oracle at hand ... and so on...). If I ever get > over to a full testing suite (no collaborators found so far...), I'll > probably be able to do more consitent testing of all modules. As I'm the one who wrote (or rather ported) the postgres module, I would be willing to help debugging/valgrinding it. Unfortunately, I have not yet completely understood how the files tests/ work. To be honest, I have just started looking at it. What would you suggest as a way to test ompgqsl in particular? Simply run rsyslogd with valgrind and throw messages against it? Regarding GSSAPI: As I'm a big fan of Kerberos I will definitely give it a try as soon as I have some spare time, maybe I can help in valgrinding it, too. Regards, Jakob (aka sur5r) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkl/TU0ACgkQ1YAhDic+ada31QCgu1f54fx4XMNpLjrASZ2fGIJ8 V8sAoKD8hRx7tuRzpwkajg5PPCDkwnLY =luw3 -----END PGP SIGNATURE----- _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
