[RADIATOR] Code and config changes without restart?

[Hugh Irvine]

Hello Jared -

Hook code and the configuration file are loaded at run time and whenever you send a HUP signal to the process.

See section 6.0 in the Radiator 4.9 reference manual.

See also the Monitor section (25 in the manual) and our companion Radar product.

regards

Hugh


On 30 Dec 2011, at 12:36, Jared Watkins wrote:

> I'm using an external file for testing some hook code and I'm wondering if that is only loaded at startup or if it would be reloaded from disk if the file changes?  If not.. how difficult would that be to add?  I'll admit I've not spent much time going through the unencrypted portions of your server. 
> 
> I'm also looking at using memcached for another part of this project and I'd like use it here for propagating runtime config changes into the running radius server. It would need a persistent connection opened by the main daemon similar to a db connection.. for frequent 'get' operations by the hook code.  Thoughts on that? 
> 
> The point of all this is to have to shutdown the radius server as little as possible once it's in production.  I'll be looking at other ways of ensuring a listener is always available of course.. but these things would make that easier to manage. 
> 
> Thanks,
> Jared
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
hugh at open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. 
Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.