Dynamic clients

Aaron Hurt ahurt at ena.com
Mon May 11 20:26:02 CEST 2015

That sounds very logical to me and should avoid a lot of unnecessary reloads.  Are you thinking a simple modification time check or some sort of file hash?

— Aaron

> On May 11, 2015, at 10:34 AM, Alan DeKok <aland at deployingradius.com> wrote:
>  No one uses this much, but it could be better documented and used.  I had a thought which might help...
>  Right now there's a "dynamic_clients" module.  It reads the dynamic clients from a file.  The "lifetime" parameter determines when the client should be reloaded.
>  It would be useful to automatically extend the lifetime if the origin file still existed, and was unchanged.
>  i.e.
> 1) create dynamic client with lifetime = 300 (so you can change it periodically)
> 2) 300s later, the server notices that the file exists, and hasn't changed
> 3) the server extends the client for another lifetime.
>  Thoughts?
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20150511/73ebb770/attachment.sig>

More information about the Freeradius-Devel mailing list