Hello Jaafar -
Given the sizes of your /etc/paswd and /etc/shadow files, I am not surprised that Radiator is taking so long to start up. You should really be using an SQL database for such large user populations. regards Hugh On Tuesday, September 3, 2002, at 02:14 PM, Jaafar Bin Sarim wrote: > Hello Hugh > > I'm running 5 instances of radiusd operating in one server 256M RAM > and CPU 200MHz Ultra sparc1. > > Each of the 5 instances takes this much time to start as shown below: > > #/var/run 539$ time rad-roamin start > > real 0m53.145s > user 0m44.750s > sys 0m1.800s > > The sizes of /etc/passwd and /etc/shadow in the server are as follows: > -rw-r--r-- 1 root staff 21215436 Sep 3 11:37 /etc/passwd > -r-------- 1 root staff 10251013 Sep 3 11:37 /etc/shadow > > We're running on Radiator version 3.1 > > We're updating our /etc/passwd and /etc/shadow every hour and the 5 > radius instances seem to be caching every hour as well. > This result in unavailability of the 5 radius instances. > > Are there any tips to improve performance or avoid any recaching > overlaps. > > Thank you. > > > Best Regards > Jaafar Sarim > SingNet > > > > -- 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.
