[debian-mysql] Bug#609537: /etc/init.d/mysql stop leaves a process but exits with 0 status

Laurent Bigonville bigon at debian.org
Wed Apr 27 12:34:32 UTC 2011


Also as an opposite, the initscript could return 1 even if the daemon
has started successfully.

I see this on one of my server with innodb_buffer_pool_size = 33G and
memlock as the process take some time (more that the 14s allowed in the
init to start).

Should an other bug be opened for that one?


Laurent Bigonville

More information about the pkg-mysql-maint mailing list