Re: problem with using rlm_sql for accounting only

On Tue, 2005-08-09 at 00:01 +0200, Nicolas Baradakis wrote: John Donagher wrote: If the SQL server is inaccessible (i.e. down, or locked), freeradius rejects all radius requests. In my case, since the SQL database is being used only for accounting, this is not desired behavior. The

Re: problem with using rlm_sql for accounting only

On Mon, 2005-08-08 at 18:09 -0400, Alan DeKok wrote: John Donagher [EMAIL PROTECTED] wrote: If the SQL server is inaccessible (i.e. down, or locked), freeradius rejects all radius requests. In my case, since the SQL database is being used only for accounting, this is not desired behavior.

Re: problem with using rlm_sql for accounting only

John Donagher [EMAIL PROTECTED] wrote: Indeed.. under normal circumstances it wouldn't go down. My issue is that the SQL server is not a critical part of our infrastructure and I don't want it to be (at this point anyway). I'm using it for accounting trend reporting only.. in any event,

problem with using rlm_sql for accounting only

Hi all- I've recently deployed freeradius at my employer to replace our old radius server which lacked native LDAP support which we've moved to for authentication and authorization. Thanks for a great application. I have one problem: I've configured freeradius to send accounting data to an SQL

Re: problem with using rlm_sql for accounting only

John Donagher wrote: If the SQL server is inaccessible (i.e. down, or locked), freeradius rejects all radius requests. In my case, since the SQL database is being used only for accounting, this is not desired behavior. The link below explains how to control the flow of modules in FreeRADIUS.