FreeRADIUS starts in seconds. I have restarted FreeRADIUS in very large production environments without a problem. If you are concerned about availability, use multiple FreeRADIUS servers and/or a load balancer (F5, Cisco, lvs, etc.). Tim From: freeradius-users-bounces+tim.sylvester=networkradius.com@lists.freeradius.or g [mailto:freeradius-users-bounces+tim.sylvester=networkradius.com@lists.freer adius.org] On Behalf Of Rameshbabu Ragothaman Sent: Monday, May 31, 2010 12:30 PM To: freeradius-users@lists.freeradius.org Cc: aland@nitros9.org Subject: Re:Re: How long is the nas-table cached by freeradius? Is this fix available now ? (freeradius server to read the change in nas-table without restart) Thanks. Evert Meulie <evert@witelcom.com> wrote:

Just wondering about the following: If a change is made in the nas-table of the radius-db, how long does it take for the freeradius daemon to start using this updated info? Or is the nas-table only read at freeradius (re)start?

It's only read at re-start. It could be fixed, but it's not a high priority. Alan DeKok.

Rameshbabu Ragothaman <rameshbabu.ragothaman@ibec.net> writes:

Is this fix available now ? (freeradius server to read the change in nas-table without restart)

Looks like I've expired the rest of this thread so this might have been brought up before, but did you check out the raddb/sites-available/dynamic-clients example? This may solve your problem, depending on your requirements. Bjørn