For some time we've had an intermittent problem where freeradius becomes
unresponsive, consuming at least 98% of the CPU. A 'kill -TERM' will
sometimes kill the daemon, but usually a 'kill -9' is needed. This
always seems to happen right about when we reload the config (with a
HUP), or stop and
George C. Kaplan [EMAIL PROTECTED] wrote:
I'm guessing that the daemon can hang if it gets a signal just as the
rlm_krb5 module is called. It's marked RLM_TYPE_THREAD_UNSAFE, so it
gets a mutex, and attaching gdb to the hung daemon showed:
That's bad.
Is anyone aware of any freeradius
2 matches
Mail list logo