29-Jan-03 at 05:27, Alan DeKok ([EMAIL PROTECTED]) wrote : > Simon White <[EMAIL PROTECTED]> wrote: > > Just maybe, there is an argument for some fallback code in the > > freeradius source, > > The rlm_sql module and *some* of it's drivers were updated in 0.8 to > do re-connects. However, some of the drivers are not actively > maintained, and weren't patched. > > > but somewhere in the back of my mind configurable > > failover is your best bet anyway. If the downtime on your DB server is > > predictable, you don't have a problem anyway. If not, get Radius to > > failover to somewhere else. Instead of me re-reading configurable > > failover docs, have a look yourself and come back to the list with > > questions. > > Configurable fail-over won't help here, as the database connections > will *never* come back up. > > Sending a HUP signal to the server may help in the short term.
Configurable failover was just a thought. Like, if it failed over to another DB then what happens when the original DB comes up? Is there a preference? This is a rhetorical question. I just don't have time to go find & read the docs right now. -- |-Simon White, Internet Services Manager, Certified Check Point CCSA. |-MTDS Internet, Security, Anti-Virus, Linux and Hosting Solutions. |-MTDS 14, rue du 16 novembre, Agdal, Rabat, Morocco. |-MTDS tel +212.3.767.4861 - fax +212.3.767.4863 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
