I am not stuck on how it should work. I already found solution how faster detect that db fail and how FR can check this state, without stuck on checking DB. Solution is very simple. 1) external script which check db (detect time ~6-8 sec) and write this status to file 2) perl script in FR which read status from file and depending on status send or not request to db Using file for transfering state between script and FR not the best solution but I didnot found anything better(I will be happy if you can recommend better ) \ AK
On 18 Jul 2023, at 22:39, Alan DeKok <aland@deployingradius.com> wrote:
On Jul 18, 2023, at 12:45 AM, Anatoliy <cphlpd@gmail.com> wrote:
Hi Alan, there are 2 options how DB can fail.
That's nice.
You seem to be stuck on how things *should* work.
I've explained why things work the way they do, and what limitations are creating the current behavior. I've explained what we're doing to fix it. I've explained how you can help.
This is how it works. It's not productive to keep wishing that things were different.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html