Recent cleanups

[Alan DeKok]

Joe Maimon wrote:
> This sounds too good to pass up. Sigh. Gotta rebase and rebuld off cvs 
> head again now.....

  branch_1_1 has the same fixes, IF you wait for all of the requests to
be cleaned up.  I haven't yet gotten around to having it clean up the
request list on exit.

   Again:

$ radiusd -m -Xd ./raddb

  Means that you can run the server, and once it's been idle for 5
seconds, hit ctrl-C.  Anything you see using "valgrind --tool=memcheck"
other than ltdl.c is a memory leak that needs to be fixed.

> root      5122  5122  0.0    8  1.2 116796 13340 ?        Ssl  Feb09 
> 1:32 /usr/sbin/freeradius

  Maybe you have a busy server?  Without more information, it's hard to
tell.

  Most of the changes I just added are for proper cleanup at exit.  So
they don't affect the normal running of the server.  They do, however,
make it a lot easier to read the output.  There's less noise, which
means the real leaks are obvious.

  Alan DeKok.
--
  http://deployingradius.com       - The web site of the book
  http://deployingradius.com/blog/ - The blog