Date: Thu, 30 Nov 2006 11:20:14 +0200 (EET) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Andrew Pantyukhin <infofarmer@FreeBSD.org> Cc: ports@FreeBSD.org Subject: Re: apache + php + mysql startup order Message-ID: <20061130111229.E14131@atlantis.atlantis.dp.ua> In-Reply-To: <cb5206420611300107x689fccf0r1904e2e8365fcb93@mail.gmail.com> References: <20061130103911.E14131@atlantis.atlantis.dp.ua> <cb5206420611300107x689fccf0r1904e2e8365fcb93@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Thu, 30 Nov 2006, Andrew Pantyukhin wrote: > On 11/30/06, Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> wrote: >> I'm trying to write an automated rc.d-script that should >> check MySQL database before it's used by the >> Apache+PHP hosting. > > If I were you, I'd make my php scripts handle temporary > db outages. Don't forget that most hosting providers have > web and sql servers on separate machines. You seem to miss my point - I'm sysadmin, _not_ webmaster, so those scripts are not mine. Let every person handle he's own set of tasks ;) I just want to ensure that apache+php (or +CGI or whatever) will not access broken DB before it's repaired. There is a non-zero probability for DB to be damaged due to power supply outage, but 'mysqlcheck -r' always fixes those damages for me - so why don't automate this procedure? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061130111229.E14131>