I need a solotion to make logging of accounting as robust a possible.
Currently I am running an authenticating and an accounting Radiator server
as separate processes, so accounting hickups cannot influence authentication
and v.v.
Part of the accounting info needs to be put in an Oracle database while
still putting full accounting in standard 'detail' files.
Currently I have the same accounting process doing both logging to files
and Oracle, but when Oracle gets too slow I also loose file contents because
the single-threaded nature of Radiator causes it to drop UDP packets.
What is the best solution to avoid losing detail records ???
Is proxying to an other Radiator process the solution ??
Regards
Paul van der Zwan
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
