Hello Griff -
>
> I'm new to this list so please bear with me if I'm verbose. I have a
> customer AuthBy module that needs to do several SQL database accesses
> and will definitely be slow, requiring a process fork. I read in the
> manual about using AuthGeneric::handlerFork, but I have an over-riding
> version of handle_request and I guess that is why
> the AuthGeneric::handlerFork could not be found. I put handlerFork in my
> custom module and it seems to work in that it does create child
> processes and eliminates them, most of the time. On my testing
> environment where I'm only sending it one request at a time using the
> radpwtst program, it performs wonderfully. However, in the production
> environment where it is getting at least a request per second, after 10
> or 15 minutes there are 50-75 defunt radius processes chewing up CPU and
> memory. If I leave it for a couple of hours it will overrun the machine
> and bring it down. Any suggestions?
>
Are you really sure you need to use a Fork? I would be more inclined to try
to speed up the database by improving the indexes, and/or using stored
procedures or whatever.
In general you should not be doing much else in Radiator than
username/password checking and rudimentary accounting (ie. writing accounting
records as quickly as possible).
Perhaps you could describe your requirements in more detail?
Also, what version of Radiator are you running (you should be using Radiator
2.17.1)? Could you also supply us with a copy of your configuration file (no
secrets) together with a trace 4 debug from Radiator showing what is going on.
It would also be helpful to know what hardware/software platform you are
using and what version of Perl.
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.