Hi Hugh, I have managed to solve the problem. What I did was to 1. create a soft link called radiusdhttp to radiusd file in my second install directory. 2. I edited the /etc/init.d/radiatorhttp file and changed the following lines from:
RADIUSD=/usr/bin/radiusd RADIATOR_CONFIG=/etc/radiator/radius.cfg (under the stop( ) subroutine) killproc radiusd TO: RADIUSD=/radiatordb/radiatorhttp/radiusdhttp RADIATOR_CONFIG=/radiatordb/radiatorhttp/radius.cfg (under the stop( ) subroutine) killproc radiusdhttp So, now I have two servers running perfectly and can be controlled with the Linux service command. NB: It seems the killproc command uses the name used to start the process rather than the process id etc. Regards, Tunde Itayemi. ----- Original Message ----- From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Ayotunde Itayemi" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 13, 2003 11:45 PM Subject: Re: (RADIATOR) Re: website access / ipass authentication > > Hello Tunde - > > I am afraid I can't help you with questions about "service" as I don't > use it. > > I generally use the "restartWrapper" utility included in the "goodies" > directory. > > regards > > Hugh > > > On Monday, Jan 13, 2003, at 23:38 Australia/Melbourne, Ayotunde Itayemi > wrote: > > > Hi Hugh, > > > > OK. I have manually installed a second copy of radiator in > > /radiatordb/radiatorhttp directory. > > I have changed the port accordingly. > > I made a copy of the /etc/init.d/radiator file and save it as > > /etc/init.d/radiatorhttp > > I edited radiatorhttp to reflect the config of my new radiator install > > and > > used the > > RH chkconfig to add the service to the system. > > The problem I noticed now is that when I use the "service" command on > > radiatorhttp > > it appears to work on my original radiator installation! > > "service (start/stop/restart/status) radiatorhttp" actuallly works on > > my > > radiator service > > and not radiatorhttp. Any ideas? > > > > Please find attached my /etc/init.d/radiator & /etc/init.d/radiatorhttp > > files. > > > > Regards, > > Tunde Itayemi. > > > > ----- Original Message ----- > > From: "Hugh Irvine" <[EMAIL PROTECTED]> > > To: "Ayotunde Itayemi" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Saturday, January 11, 2003 5:25 AM > > Subject: Re: website access / ipass authentication > > > > > > > > Hello Tunde - > > > > If you want to use different port numbers, why not just use two > > instances of Radiator? > > > > Otherwise, have a look at a trace 4 debug to see what attributes are > > included in the radius requests that you can use. > > > > regards > > > > Hugh > > > > > > On Saturday, Jan 11, 2003, at 04:02 Australia/Melbourne, Ayotunde > > Itayemi wrote: > > > >> Hi Hugh, Hi All, > >> > >> I have the ipass netserver installed on my RADIUS server. I also want > >> to use radiator to > >> authenticate access to some webpages on the same server. The problem > >> is that the > >> config for ipass netserver and webserver authentication both use the > >> "localhost" client > >> designation. The only way out I see it to change the port that the > >> webserver uses for > >> radius authentication and configure radiator to also listen on (this) > >> extra port. > >> The issue now is how do I differentiate requests from the two ports > >> and process the > >> requests accordingly using two different "Realm" clauses - or cascaded > >> AuthBys? > >> > >> Please advice? > >> > >> > >> Regards, > >> Tunde Itayemi. > >> > >> > > > > -- > > 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. > > > > > > <radiatorhttp.txt><radiator.txt> > > -- > 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.