On Mon, Mar 31, 2014, at 10:57, Clint Byrum wrote: > It is more likely that it is a problem with the mysql sysvinit script > and mysqld itself. What is probably wrong is that mysqld is daemonizing > and returning control to the terminal before it is _actually_ ready. > > Note that in Ubuntu the upstart job for mysqld runs it in the foreground, > and the post-start _polls mysqld_ so that anything that wants to be > 'start on started mysqld' will have a working mysqld. > > Still, I would appreciate the "it doesn't work" full description too.
That's the purpose of the (adapted from Fedora) mysql-wait-ready script. It's run --with the same pid as mysqld-safe-- so that progress is held up until the server is ready. I couldn't find any --nodaemonize switch in mysqld's man page. Maybe it is daemonizing, but then there's no way to prevent that. And if that were the case it would be listening on 3306, but it's not. -- http://www.fastmail.fm - Access your email from home and the web -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
