The check for f*cked database (which otherwise sends out zillions of update failed emails) interferes with install. So what else can we do about f*cked databases which open successfully but don't actually read/write data? It would of course be nice if we didn't have to deal with them, but apparently we do. For now we're not doing anything until I can figure out how to take the site offline when it happens without affecting install.
This commit is contained in:
parent
ff7182f441
commit
e369e5ddc5
@ -29,9 +29,9 @@ function load_config($family) {
|
|||||||
// If the DB was successfully opened, but we can't read from it,
|
// If the DB was successfully opened, but we can't read from it,
|
||||||
// we must assume catastrophic failure of the DB. Report the system down.
|
// we must assume catastrophic failure of the DB. Report the system down.
|
||||||
|
|
||||||
if($r === false) {
|
// if($r === false) {
|
||||||
system_unavailable();
|
// system_unavailable();
|
||||||
}
|
// }
|
||||||
|
|
||||||
if($r !== false) {
|
if($r !== false) {
|
||||||
if($r) {
|
if($r) {
|
||||||
|
Reference in New Issue
Block a user