On 07/04/2022 01:15, Wolfgang Breyha wrote: > And with the custom OpenSSL RPMs it seems radiusd doesn't leak. At least > valgrind/memleax do not detect the SSL_do_handshake leak and radiusd memory > footprint gets stable after the first batch of requests floating at > ~110-120MB. I put this setup on one of our production hosts now to see what > happens as soon as people start connecting their WLAN devices in the morning.
Meanwhile I can confirm that my custom RPMs do not leak and radiusd memory usage only depends on the load it has to handle. So I filed: https://bugzilla.redhat.com/show_bug.cgi?id=2072962 Greetings, Wolfgang -- Wolfgang Breyha <[email protected]> | https://www.blafasel.at/ Vienna University Computer Center | Austria _______________________________________________ radiator mailing list [email protected] https://lists.open.com.au/mailman/listinfo/radiator
