Hello Edgar -
On Tue, 23 Nov 1999, Edgar Scherer wrote:
> Hi,
> evertime one of our users changes his password RADIATOR just freezes up for
> about half a minute, then resumes normal operation. This probably due to it
> re-reading the passwd/shadow-file (12.000 users) and keeps all of our users
> from authenticating in the mean time. Is there any way to speed this up or
> at least make it transparent to the user?
>
> Mon Nov 22 16:40:28 1999: DEBUG: Reading password file
> /net/etc/Radiator-2.14.1/shadow.radius
> Mon Nov 22 16:41:02 1999: DEBUG: Reading group file /etc/group
>
Unfortunately, in this case the answer is probably to use some other
user database. Because Radiator, as you rightly point out, caches the password
and group files in memory for speed of access, normal operation has to wait
until the cache is re-initialised. Most large-scale operations use some form of
SQL database to store their users and use a special web form for password
changes. There are example SQL schemas together with a buildsql utility
included in the distribution.
Another alternative is to set up Radiator to use a copy of the password file
and propogate the password file once every night. Of course this can be
confusing for users, as their password changes will only come into effect some
time after the event.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
