Query regarding redundant module and configurable failover codes

[Shweta Khadse]

Hi Fajar

Yes we REALLY tested it :)

"A quick glance says the OK block will always
be used" is what we wanted! Because this block is critical.

What was happening earlier was since we didnt have any return code for the
sql_update_**** ,any failure at that level was making the accounting module
return a false and thus the session disconnection. In our case the last two
statements are not so critical that the sessions be dropped.
So now with this approach - mission accomplished!

Regards
Shweta


On Tue, Dec 13, 2011 at 10:59 AM, Fajar A. Nugraha <list at fajar.net> wrote:

> On Tue, Dec 13, 2011 at 1:54 PM, Shweta Khadse <shwetgk at gmail.com> wrote:
> > Thankyou Alan!
> >
> > You gave us an idea about how we can set "ok" to return a default ok for
> the
> > section.
> >
> > We tested with our second approach as below and thrilled that it works/
> > This ensures radius returns ok even if the sql_update_**** modules fail.
> >
> >             redundant{
> >                      ok
> >                  }
> >             sql_update_xxxx {
> >                         FAIL=1
> >                 }
> >              sql_update_yyyy {
> >                      FAIL=1
> >                 }
> >
>
> DId you REALLY test that? A quick glance says the OK block will always
> be used, thus making sql_update* pretty much useless. Why not use
> Alan's example?
>
> --
> Fajar
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20111213/40511c6a/attachment.html>