On 04/06/2013 03:58 PM, Garry Shtern wrote: > That's an excellent idea!
Good to hear it's solved. > In my case the SQLite DB doesn't even need > to be writable by the radiator user. I put my users and clients into > that database, and created custom SQL queries and everything works > perfectly. Sounds a bit like the case I was referring to where SQLite DB is used for AuthBy SQLRADIUS. In this case an external process updates SQLite DB and maintains list of realms and next hop servers for proxying. Like in your case, the DB file itself is read-only for radiusd process. Thanks, Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
