Hello Neil - In my consulting practice I almost always find that a multi-process setup for Radiator works very well.
What this entails is a "frontend" Radiator process that listens on the standard RADIUS ports, classifies the RADIUS requests according to whatever local requirements there are, and then proxies the different streams of requests to separate "backend" Radiator processes each listening on different port numbers. This gives you controlled multi-threading with all processes able to handle requests in parallel. This approach also has the added advantage of much simpler configuration files for each Radiator instance. If you have common elements across different instances you can use "Include …" directives so you only have single definitions for those common elements. If you have any questions feel free to contact me directly. regards Hugh On 22 Aug 2012, at 04:11, "Johnson, Neil M" <neil-john...@uiowa.edu> wrote: > > Is it possible to configure RADIATOR to run multi-process/thread on windows ? > > I don't believe so, but I just wanted to confirm. > > -Neil > > -- > Neil Johnson > Network Engineer > The University of Iowa > Phone: 319 384-0938 > Fax: 319 335-2951 > Mobile: 319 540-2081 > E-Mail: neil-john...@uiowa.edu > > _______________________________________________ > radiator mailing list > radiator@open.com.au > http://www.open.com.au/mailman/listinfo/radiator -- Hugh Irvine h...@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. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
