AW: (RADIATOR) http admin config question

[Wallner Martin]

Just take the different settings for the two instances in different config-parts...

so:
--------- file1-acc.cfg -----------
ServerPort 4080
... ... other different settings
-------------------------------

--------- file-auth.cfg -----------
ServerPort 4081
... ... oither different settings
-----------------------------------

-------- radius-auth.config --------
include file-auth.cfg
include generic.cfg
-----------------------------------

-------- radius-acc.config --------
include file-acc.cfg
include generic.cfg
------------------------------------

This glues all the different settings like Ports and Monitorsettings into the standard config for the server. Normally a second 'generic' file with all the settings for both ('generic.cfg' in the example) will accompany the two different configs... now, just a bit init.d/rc.d magic, and all is set up... 

=mw=


-----Ursprüngliche Nachricht-----
Von: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] Im Auftrag von Alex Sharaz
Gesendet: Freitag, 01. Februar 2008 13:14
An: radiator at open.com.au
Betreff: (RADIATOR) http admin config question

Hi,

I'm running two instances of radiator, one for auth and one for accting.

 

I use the same config file for both these instances and use some  radius command line arguments to specify which port is being used for acct and auth.

 

As my http admin setup is i  the config file, when i do a sighup I get 1 message saying that the server has bound to the port sauccessfully and one saying (obviously) that it can't connect to the port because something else is using it.

 

Is the only way to get round this to use two config files?

alex

 


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.