Hi, I few weeks ago I posted a question about a slow radiator reaction.
I use .db files to hold my users, i have a .db file with about 209.000 users in it, and its about 20MB big. Could that be the problem? That the file is to big ? Or could it be the old radiator version I use? (1.91) If the .db file is the problem, is there a way to solve that and keep on using those .db files? Thanks. W. Systems Administrator. Uninet International NV/Planet Internet. Tel: +32 (0)3/275.15.41 -- uniX, the source is out there! On Tue, 29 Jul 2003, Hugh Irvine wrote: > > Hello Wesley - > > I generally recommend something like the following - the directories > shown are what I usually use, but feel free to use whatever suits your > particular installation. > > Create a directory to store the configuration files, hooks, db files, > etc. > > mkdir /usr/local/etc/radius > > Copy all of the above files to this directory. > > cp .... /usr/local/etc/radius > ..... > > Create a directory for the Radiator distributions: > > mkdir /usr/local/src/Radiator > > Copy the new Radiator distribution to this directory: > > cp /tmp/Radiator-3.6.tgz /usr/local/src/Radiator > > Unpack the distribution: > > cd /usr/local/src/Radiator > gzip -c -c Radiator-3.6.tgz | tar xvf - > cd Radiator-3.6 > perl Makefile.PL > make > make test > *** DO NOT DO make install *** > > Copy the dictionary file to /usr/local/etc/radius > > cp dictionary /usr/local/etc/radius > > In your configuration file set DbDir to /usr/local/etc/radius > > DbDir /usr/local/etc/radius > > Create the log directory: > > mkdir /var/log/radius > > In your configuration file set LogDir to /var/log/radius > > LogDir /var/log/radius > > Now in your startup script you will need to add a "cd > /usr/local/src/Radiator/Radiator-3.6" before starting radiusd and use > the -config_file parameter to pass the configuration file location > > cd /usr/local/src/Radiator/Radiator-3.6; perl radiusd -config_file > /usr/local/etc/radius/radius.cfg > > Doing things this way lets you keep any number of Radiator > distributions in a clean and orderly fashion, and switching between > them is as simple as changing a single line in your startup script. > > This topic has also been discussed several times on the mailing list: > > www.open.com.au/archives/radiator > > regards > > Hugh > > > On Tuesday, Jul 29, 2003, at 04:37 Australia/Melbourne, Wesley Hof > wrote: > > > > > Hi, > > > > I'm currently running 1.91, I want to upgrade to 3.6, is there a way to > > upgrade and keep my existing configfiles/hooks/berkeley.db files ? > > > > If so, what is the easy way to do it ? Or is it best to build new > > configfiles with new features? > > > > Thanks in advance for reply'ing to this post. > > > > Kind Regards, > > Wesley. > > > > Systems Administrator. > > Uninet International NV/Planet Internet. > > Tel: +32 (0)3/275.15.41 > > > > -- > > uniX, the source is out there! > > === > > 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. > > > > > > NB: have you included a copy of your configuration file (no secrets), > together with a trace 4 debug showing what is happening? > > -- > 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.
