(RADIATOR) install radiator to a separate /opt directory - no t solved despit e docs

[Tariq Rashid]

further to this - the referance manual states that:
"
Command line arguments given to radiusd will override parameter settings in
the con-
figuration file. You should consult the section on global configuration file
parameters
(See Section 6.4 on page 18) for the meaning of those parameters.
"

However - this is not happening for db_dir. Upon startup the server
complains that it cannot find the server at the location deifned in the
radius.cfg file, despite the script calling it with an alternative
	"-db_dir ./xxxxx/" 

anyone?

solved: the issue of overriding the location of the per realm/handler
accounting files shopuld be solved vby using %D dieectives, and hence the
above method should override the value of %D read by the config file - but i
need to solve the aobe first.

tariq

-----Original Message-----
From: Tariq Rashid 
Sent: 18 June 2004 12:14
To: 'Hugh Irvine'
Cc: radiator at open.com.au
Subject: (RADIATOR) install radiator to a separate /opt directory - not
solved despit e docs



my previous query last week asked about running radiator from a different
directory. eg /opt/radiator1 and others in /opt/radiator2, opt/testradiator/
and so on..

however, the esential problem is not solved. and that is described as
follows:

	* the test configurations (radius.cfg) are designed for deployment
to multiple live servers
	* these live servers use "normal" installations of radiator, with
normal locations for
		configuration and log files.
	* the test machine which will host these multiple
instances/directories will NOT
		have configuration, pid, and output files in these nomral
locations - 
		they will be kept in these separated directories. 
		for example /opt/radiator1/radius.cfg,
/opt/radiator1/logfile, 
		/opt/radiator1/detail, /opt/radiator1/radiator.pid, etc etc 
	* the aim is to configure, maybe using a startup script, which is
		start these test instances and use these "local/non-global"
file
		locations. 
	* i currenlt have a script which OVERRIDES the common radius.cfg
		parameters such as logdir, dbdir, etc etc.
		That is, if the distributed radius.cfg contains
		Logdir /var/radius/radiator, i can override this in the
		start script by passing a "-log_dir ./" to the executable.



However! The above overrides work - but create dupliate log files (same
length, same timestamp), in both the overriden location and the system
/var/log/radius/raidator... location specified in the radius.cfg. so i get
get both
/opt/radiator38/var/log/radius/radiator/2004-06-18.log and
/var/log/radius/radiator/2004-06-18.lo

Why is this?

This problem may also apply to the hook perl files and the acocunting record
detail file too - but i haven;t got that far yet!

Thanks,

tariq

- below is a rough script which will do the above overriding...

------------------------------

#!/bin/sh

# change to server directory
cd /opt/radiator38

# start server with the overridden file locations
./radiusd \
        -db_dir ./ \
        -log_dir ./ \
        -log_file ./logfile \
        -config_file ./radius.cfg \
        -dictionary_file ./dictionary \
        -pid_file ./radiator.pid

# the following additional settings are useful for debugging
        -log_stdout \
        -foreground

--
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.

--
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.