disable response for accounting

[liran kessel]

thanks, that has helped.

I guess the fail before the sql is what caused my issue.


we are running 2.2.6 and it seems to not recognise the do_not_reply. 
is there any disadvantage in using the fail rather than the do_not_reply?
I am sure there are other reasons to upgrade, but just wanted to understand if this is another one or not?

Thanks
liran

> On 14 Sep 2016, at 11:32 PM, Alan DeKok <aland at deployingradius.com> wrote:
> 
> On Sep 14, 2016, at 4:23 PM, liran kessel <lirankessel at gmail.com> wrote:
>> 
>>> 
>>> Hi,
>>> 
>>> we have a freereadius server that is only responsible for collecting accounting info from a mobile network and storing to mysql.
>>> However the network administrators have requested we don’t send back respond messages to confirm we received the message.
> 
>  In recent versions of the server.
> 
> accounting {
> 	...
> 
> 	do_not_reply
> }
> 
>>> I have found this thread from a few years ago and did as it suggested.  
>>> 
>>> http://lists.freeradius.org/pipermail/freeradius-users/2012-May/060723.html <http://lists.freeradius.org/pipermail/freeradius-users/2012-May/060723.html>
>>> 
>>> but while it seems to have stopped sending responses to the network, it stopped logging the info into the mysql DB, eventhough it continued to log to the detail log file. and so I had to roll back.
> 
>  if you put "fail" as the last thing in the "accounting" section, it will still write to MySQL.
> 
>>> Can anyone explain why this caused the server to stop writing to mysql?
> 
>  You put "fail" before "sql".
> 
>  Alan DeKok.
> 
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html