> This would explain what we currently see. It seems to be TLS-related, > as you > said. So it is unlikely to be a message at all, but rather a TLS event > that > causes the mem leak. With that said, I should probbably see if a > connection > abort can trigger one...
Just for the records, the connection aborts I triggered did NOT result in leaked memory :( Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
