When i played around with this setup, and i needed to run a few instances with identical configs but on different IPs, i found using a GlobalVar to be very useful. set the IP or port in each radius by passing it via a GlobalVar on the command line, then you can use it to set various items that can't be shared between instances, like PidFile and Logs. I'm not doing it that way anymore, but i think it went something like this:
/usr/local/sbin/radius IpAddress=10.1.1.2
config file: BindAddress %{GlobalVar:IpAddress} PidFile /var/run/radius.%{GlobalVar:IpAddress} LogFile /var/log/radius/logfile.%{GlobalVar:IpAddress}
and so on.
- jeremy
At 10:56 AM 6/5/2003, you wrote:
On 6/5/03 2:20 AM, "Mike McCauley" <[EMAIL PROTECTED]> wrote:
> On Thu, 5 Jun 2003 03:58 pm, jaws wrote: >> Got it. That means i can also use the same config file? > > Yes, if you use the -auth_port and -acct_port command linet flags. > > Cheers.
Be careful on this. If you have entries in the config that use files for logs, etc, the two processes could step on each other causing a major problem.
-- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] PGP: http://www.inoc.net/~dev/ Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9
Hackers have kernel knowledge.
=== 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.
=== 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.