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@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