Bug 114621 – Mysql 5.0.16-r3 init script does not allow enough time to start

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Simon Detheridge 2005-12-06 06:15:12 UTC]

On my server, it takes mysql longer than 10 seconds to start. This is because I
have a large number of complex databases. The init script allows 10 seconds for
the mysqld socket to appear, before terminating reporting failure. 

(I then can't stop the mysql server using the init script, as it thinks it's not
started... I have to killall mysqld)

The length of time the init script is defined by the maxtry variable, defined at
line 209.

I recommend either: a) increasing this value to 30 seconds, or b) making this
settable in /etc/conf.d/mysql

[Comment 1 Francesco R. (RETIRED) 2005-12-07 15:19:28 UTC]

Created attachment 74261 [details]
/etc/init.d/mysql

try to adapt your /etc/conf.d file and then issue a 
#/etc/init.d/mysql stop start stop
with the attached script

if something fail, please send the output of:
#DEBUG=4 /etc/init.d/mysql stop start stop

[Comment 2 Francesco R. (RETIRED) 2005-12-07 15:22:59 UTC]

Created attachment 74262 [details]
/etc/conf.d/mysql

and here is the conf file.

Thanks for your suggestion

[Comment 3 Francesco R. (RETIRED) 2005-12-07 15:49:18 UTC]

Created attachment 74268 [details]
/etc/init.d/mysql

Forgot to add a workaround for the charset/collation issue of Bug #111809.

[Comment 4 Francesco R. (RETIRED) 2005-12-08 07:51:06 UTC]

Changes are in CVS now, closing, feel free to reopen if it's still missing
something.