Bug#430684: [debian-mysql] Bug#430684: Bug#430684: Calculating the timeout instead of, using a configuration setting.

2007-07-27 Thread Paul Veldema
I have entered the agreement and recieved the automated 'contribution' reply: 'Signed Contributor Agreement #54 from Paul Veldema'. With regards, Paul Veldema On Fri Jul 27 01:33:39 CEST 2007 Monty Taylor <[EMAIL PROTECTED]> wrote: ... Ok. I haven't wa

Bug#430684: [debian-mysql] Bug#430684: Calculating the timeout instead of, using a configuration setting.

2007-07-03 Thread Paul Veldema
From sean: - /proc/meminfo is linux specific and less general. perhaps you could write something with "free" or some other generic utility instead? Just for fun, here the version using 'free': mysql_startup_timeout() { memtotal="`free -k | head -2 | tail -1| cut -d ':' -f 2 | tr -s

Bug#430684: Calculating the timeout instead of using a configuration setting.

2007-06-27 Thread Paul Veldema
Hello, Here some more suggestions and a flexible solution that does not need an extra configuration setting. Since there is a relation between the timeout and the memory to be allocated by mysql, a timeout setting is not nescessary. Simply calculate the the timeout, there are two options:

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

2007-06-26 Thread Paul Veldema
Package: mysql-server-5.0 Version: 5.0.32-7etch1 When using an innodb_buffer_pool_size of 24GByte (or more) I get a "failed!" message starting mysql with '/etc/init.d/mysql'. Mysql starts anyway, however /etc/mysql/debian-start is not started. This happens because of a 14 second timeout in the /e