Avoid restart freeradius on config update to modules

[Suriya Shankar]

Thanks Alan.

It's a RadSec connection, On each restart the connection between the NAS
and the Radius Server drops and reestablishes on the next authentication.
By making the EAP module HUP'd I noticed the established connection was
unaffected but yes the clients had to re authenticate again. Is my
understanding correct?

Regards,
Suriya

On Fri, Jan 10, 2025 at 8:30 PM Alan DeKok <aland at deployingradius.com>
wrote:

> On Jan 8, 2025, at 5:53 AM, Suriya Shankar <suriya.dshankar at gmail.com>
> wrote:
> > I am working with the freeradius branch 3.0.27 and freeradius service
> > constantly restarts when a module is updated with new config as per
> design.
> > I went through previous questionnaires on the same and understood it
> works
> > as expected.
> >
> > I made a few changes in the code and tested, I am able to successfully
> > reload the configuration instead of restarting the freeradius server.
> Added
> > the diff for your reference. If this is good, can I create a PR
>
>   I don't think this will work.  Or at least, it won't do what you want.
>
>   The EAP module tracks ongoing EAP sessions in internal data structures.
> If the module is HUP'd, it will reload its configuration, and then start a
> brand new tracking structure.
>
>   The result is that all ongoing EAP sessions will fail.  This isn't
> really any different than restarting the server.
>
>   Rather than sending a patch, perhaps you could describe the problem
> you're trying to solve.  It isn't just "HUP a module", it's something more
> specific than that.
>
>   Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/devel.html
>