[debian-mysql] Bug#430684: Bug#430684: "/etc/init.d/mysql start" timeout with large innodb_buffer_pool_size on X86-64 systems.

[sean finney]

heya,

On Tuesday 26 June 2007 23:06:28 Monty Taylor wrote:
> We've actually been working on this upstream and have put in support to
> specify the timeout value in the my.cnf file, as there is really no
> "perfect" timeout value here.
>
> I'll see if I can forward/point out some of the work we've done...

alternatively (and much easier probably), the init script code in question 
could be replaced with something more flexible.  i.e.:

            /usr/bin/mysqld_safe > /dev/null 2>&1 &
            # 6s was reported in #352070 to be too few when using ndbcluster
            for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14; do
                sleep 1
                if mysqld_status check_alive nowarn ; then break; fi
                log_progress_msg "."

could be replaced by

            /usr/bin/mysqld_safe > /dev/null 2>&1 &
            # 6s was reported in #352070 to be too few when using ndbcluster
            for i in `seq $STARTUP_TIMEOUT`; do
                sleep 1
                if mysqld_status check_alive nowarn ; then break; fi
                log_progress_msg "."

and then let STARTUP_TIMEOUT be defined in /etc/default/mysql-server 
(or /etc/sysconfig/mysql-server for the redhat folks, etc).

similar there looks t o be similar shutdown timeout too.

	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20070627/536a6584/attachment-0001.pgp