Hi,
i want to integrate a complete fallback, if the database isn't working like
client-auth, user-auth or accounting radiator should be use flatfiles. If
accounting cannot be write to mysqldb it is written to a
flatfile(AcctLogFileName ).
I think for the user I only write
<Realm bla>
<AuthBy SQL>
DBSource dbi:mysql:cndps
DBUsername radiator
DBAuth *****
AuthSelect SELECT password,NULL,replyattr FROM snapshot
WHERE \
loginname='%U' AND realmname='%R'
NoDefault
# You may want to tailor these for your ACCOUNTING table
# You can add your own columns to store whatever you like
AccountingStopsOnly
AccountingTable accounting
AcctColumnDef username,User-Name
........
AcctColumnDef disconnect_cause,Ascend-Disconnect-Cause
</AuthBy>
# use this for fallback
<AuthBy FILE>
Filename users
</AuthBy>
AcctLogFileName accounting.log
PasswordLogFileName password.log
</Realm>
How must I do that the accounting-data(stoprecord) first written to the
mysqldb if anything go wrong it will be written to a
flatfile(AcctLogFileName) - is it possible or if the accounting data will be
lost?
I think the handler for the realm is ok it will at first look into the
mysqldb, if the mysqldb is down it will use the flatfile.
Now one of my Problem is who can I say radiator to look for client auth at
first to mysqldb via:
<ClientListSQL>
DBSource dbi:mysql:cndps
DBUsername radiator
DBAuth *******
GetClientQuery SELECT name, radius_secret, NULL, NULL,\
'cybernet', vendor \
FROM \
client
</ClientListSQL>
If this go wrong it look into a seperate file e.g. clients?(only if the
database is down); can you give me hint how to write it in the config file?
Thanks.
Our System: FreeBSD 4.0, Radiator 2.16, Perl 5.005_03 built for i386-freebsd
The System with the SQL-Database is running.
Matthias Fechner
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
