|
We're using a variation on 1.2 below. Works like a champ.
>
> I have doubts if patching ldirectord is the right approach. Please
> consider more solutions that work independently of ldirectord. For
> example:
>
> 1. Localizing your problem/defensive programming:
>
> Your webservers should be able to react sensitively to a database
> failure without relying on ldirectord anyway. Do they?
>
> 1.1 If the page they generate is OK for a user, there is no need to
> tell ldirectord anything about the problem
>
> 1.2 If they can generate a special page that says, for example
> "status=nodb" instead of "status=ok", you can simply test for
> "status=ok" in the ldirectord
>
|
