From e369e5ddc53e6a0d489ceaed0bd13849c7d031f1 Mon Sep 17 00:00:00 2001 From: friendica Date: Fri, 4 Oct 2013 14:42:18 -0700 Subject: 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. --- include/config.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'include') diff --git a/include/config.php b/include/config.php index ccd907424..bccf0737f 100644 --- a/include/config.php +++ b/include/config.php @@ -29,9 +29,9 @@ function load_config($family) { // 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. - if($r === false) { - system_unavailable(); - } +// if($r === false) { +// system_unavailable(); +// } if($r !== false) { if($r) { -- cgit v1.2.3