Hello Christophe -
On Sat, 09 Sep 2000, Christophe Wolfhugel wrote:
> Carles Xavier Munyoz Bald� :
> > I have been having problems with the authentication and accounting
> > traffic. The UDP authentication/accounting ratio traffic was so high
> > that the Radiator process was unable to handle it.
> > I have tried to increment the buffer size for the UDP sockets with the
> > SocketQueueLength configuration parameter, but this has lead me to more
> > problems.
>
> I would rather suggest to reduce the size of SocketQueueLength in order
> to avoid retransmissions to be in the same waiting queue as the initial
> request.
>
> > The Radiator is a sequencial process (there is no fork) Why ? I believe
> > that will be a better RADIUS server if it were concurrent. Is there any
> > future concurrent version of the Radiator ?
>
> We use multiple instantiations of Radiator on some hosts (but they do not
> serve the same set of NASes). I guess that being able to have multiple
> instances of Radiator on the same socket would be great. It might add
> complexity, requiring file locking for the logs.
>
> Mike, is there a multithreaded Radiator planned sometime in the future ?
>
See my reply to Carles, but yes we are planning to implement a multi-threaded
version of Radiator as soon as Perl has solid multi-threading support.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
