Hello Jos� -
Have you tried using "Fork" in the AuthBy clause? Why do you say it doesn't work?
I myself am not sure whether "Fork" will work or not, but you can do some testing to find out.
Alternatively you can use multiple instances of Radiator (possibly on multiple hosts) with a load balancer in front. You may find the AuthBy ROUNDROBIN/VOLUMEBALANCE/LOADBALANCE clauses useful for this. See section 6.43 in the Radiator 3.7.1 reference manual.
At the very least you should run one instance for authentication and another instance for accounting.
regards
Hugh
On 07/12/2003, at 9:07 PM, Jos� Borges Ferreira wrote:
Hi!
I have a system that provide me a crippled ldap interface to authenticate users. So far so good.
The problem is that that system takes about 500 ms to respond, altought i can make parallel resquests and get a throughput of 80 auths/sec.
Since i cant fork LDAP auth requests which alternatives do i got to have better performace in Radiator?
Jos� Borges Ferreira
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. - CATool: Private Certificate Authority for Unix and Unix-like systems.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
