Hello Anand -
On Thu, 02 Dec 1999, Anand Buddhdev wrote:
> I read in the documentation that it is not normally necessary to set
> Forking for the AuthBy File module, because it's usually so fast.
>
> We have a situation here, where we use the pmwho program to query our
> NAS's to double-check whether a user is actually logged in or not. Some
> of our NAS's at our POP's respond slowly, because they are on slower links,
> and this seems to hold up authentication for all queries while Radiator
> does this query. Would it help to set the Fork parameter on AuthBy File
> in this case?
You need to consider the impact that a Fork is going to have on your overall
system. Keep in mind that its the whole Radiator process that will Fork, not
just the AuthBy module. You can certainly try some experiments, but YMMV.
The real answer to performance issues of this kind (other than faster links...)
is multi-threading support in Perl which will allow us to run each Radiator
request in a separate thread. We have plans for this but it will likely be well
into next year before this gets to the top of the development list.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
