Date: Sat, 11 Jun 2016 20:52:43 +0300 From: abi <abi@abinet.ru> To: ports@freebsd.org Subject: Re: wait for mysql availability Message-ID: <575C4FEB.3030801@abinet.ru> In-Reply-To: <20A7440D-80E1-4E2A-BAC4-713DC97CB949@grem.de> References: <575BEC94.70209@abinet.ru> <11C24D0E7B6E9F7E2D80B5C3@atuin.in.mat.cc> <20A7440D-80E1-4E2A-BAC4-713DC97CB949@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Yep, that's innodb. It can warm up less than a second, but it's enough sometimes. Actually, from my point of view, mysql loader should return control after it's properly initialized. I doubt every port maintainer must invent their own bicycle if port depends on mysql. On 11.06.2016 19:40, Michael Gmelin wrote: > >> On 11 Jun 2016, at 08:11, Mathieu Arnold <mat@FreeBSD.org> wrote: >> >> >> >> +--On 11 juin 2016 13:48:52 +0300 abi <abi@abinet.ru> wrote: >> | Hello, >> | >> | I have a daemon depended on mysql database, however >> | REQUIRE: mysql >> | is not enough as mysql databases are not available immediately after >> | mysql start, so my daemon fails to start. >> | >> | Are there any way to check mysql availability that would by mysql setup >> | agnostic? >> | >> | I have 2 ideas: use sleep() or standalone script using application >> | credentials in prestart. >> >> The mysql server should be ready to use after its rc script returns, you >> should open a PR with mysql for this to be fixed. >> >> > There's a difference between starting MySQL and it becoming available to clients, e.g. when innodb is recovering from a crash, which can take a long time and is not necessarily something you want to wait for on boot. > > - m > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?575C4FEB.3030801>