Hello Chris -
You are correct.
The authentication instance should have this:
AuthPort 1645
AcctPort
and the accounting instance should have this:
AuthPort
AcctPort 1646
Note that the accounting instance must have the Client clauses too.
You can also use a single configuration file and use GlobalVar's for
parameters which would be set on the command line for each instance.
regards
Hugh
On Thu, 18 Apr 2002 10:34, Chris M wrote:
> I have been reading the manual and of course working with Radiator for
> awhile. I've been pretty happy with my config for the most part and
> haven't had the urge to change much. I guess now I have the urge.
>
> What I'd like to do is create two instances of Radiator, one that monitors
> the accounting port and one that monitors the authentication port. I'm
> trying to figure out how to split the config file into two config files and
> run two instances of Radiator, one on 1645 and one on 1646.
>
> It seems like I'd want to split it up along these lines:
>
> Auth Instance
>
> - definitions of clients and their secrets
> - authentication against SQL database
>
>
> Acct Instance
>
> - accounting into SQL database
>
>
> In other words, the SessionDatabase I believe needs to be referenced by
> both authentication and accounting instances, but the AuthBy SQL clauses
> for accounting and authentication would be split among the two instances.
>
> Can anyone think of anything else I'd need to do?
>
> The motivation for splitting these isn't really just availability. I've
> noticed that in a single instance run of Radiator, that when people in
> billing do large queries of the accounting data it hangs the authentication
> process. When I turned on Trace 4 and tail -f'ed the raw Radiator log I
> noticed that while a large accounting query is running authentications
> would continually time out. This seemed very weird to me, so I was also
> wondering if anyone could think of a reason why MySQL would appear to be
> hanging this way? It seems like the queries to the database would be
> pipelined, but I'm no expert on MySQL internals. Would this behavior go
> away if I chose a different database?
>
> Thanks for the tips,
> Chris
>
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
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.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
