Alexander Clouter <alex@digriz.org.uk> wrote:
I have shitty news and really shitty news.
The 'good' news, I know FreeRADIUS (2.1.x branch) has a memory leak. The bad news, I'm running in production FreeRADIUS on ARM boxen so things like valgrind are not an option. All I see is a SIGKILL.
Spiel from top :) ---- 4260 freerad 20 0 411m 354m 3708 S 4.3 70.4 31:40.31 freeradius ----
What I do have is a 420MB core file of that above process..any takers :)
Ideas welcomed.
The best I have to offer at the moment is: ---- alex@berk:/usr/src$ strings core.4260 | sort | uniq -c | sort -r -n | head -n10 77245 Acct-Delay-Time = 0 72478 Realm = "NULL" 69890 Acct-Authentic = RADIUS 68526 Operator-Name = "1soas.ac.uk" 67717 Service-Type = Framed-User 67670 NAS-Port-Type = Ethernet 67670 NAS-Identifier = "switches" 67670 Huntgroup-Name = "cisco" 55646 Acct-Status-Type = Interim-Update 44341 Cisco-AVPair = "connect-progress=Call Up" ---- Well, it looks like something in the accounting side of things. /me goes back to pondering Cheers -- Alexander Clouter .sigmonster says: If we all work together, we can totally disrupt the system.