Hello Julio -
At 11:20 +0100 18/12/00, [EMAIL PROTECTED] wrote:
>hi radiators,
>
>our scenario is a 3-layer architecture with the following:
>
> NAS Clients -> Proxy Radiator -> Radiator (with mysql in local) -> LDAP
>
>We are making some tunning in the systems. In case of Radiator we set
>"SocketQueueLength"
>up to 150000.
>
>So anyone has made tunning of Radiator, mysql, LDAP or tcp in a similar
>architecture?
>
>We're using Solaris, any recommendations in tcp tunning in a Radiator
>environment?
The place to start for tuning purposes, is a trace 4 debug so you can
see where your timje is being spent. In the environment described
above, I would suspect the vast majority of the delays to occur in
the SQL and LDAP processing.
There have been various discussions about performance on the list, so
check the archive site:
http://www.starport.net/~radiator
regards
Hugh
--
NB: I am travelling this week, so there may be delays in our correspondence.
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.
