List:Bugs« Previous MessageNext Message »
From:Sinisa Milivojevic Date:March 11 2003 1:43pm
Subject:Re: mysqld in an infinite loop
View as plain text  
Christopher Chan writes:
> 
> [mysqld]
> datadir=/var/lib/mysql
> socket=/var/lib/mysql/mysql.sock
> set-variable = thread_cache_size=700
> set-variable = table_cache=850
> set-variable = key_buffer_size=16M
> set-variable = max_connections=850
> set-variable = max_connect_errors=999999999
> skip-name-resolve
> skip-locking
> memlock

Hi!

First of all, try not using memlock.

Second, when MySQL runs out of memory, which is a possibility here, it
will print the error message in the error log file.

Third, try to achieve the same effect with our binary, as you could be
running out of system space with glibc default stack size.


-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <sinisa@stripped>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Fulltime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
       <___/   www.mysql.com

Join MySQL Users Conference and Expo:
http://www.mysql.com/events/uc2003/

Thread
mysqld in an infinite loopChristopher Chan11 Mar
  • Re: mysqld in an infinite loopAlexander Keremidarski11 Mar
  • Re: mysqld in an infinite loopChristopher Chan11 Mar
  • Re: mysqld in an infinite loopChristopher Chan11 Mar
    • Re: mysqld in an infinite loopSinisa Milivojevic11 Mar
      • Re: mysqld in an infinite loopJeremy Zawodny11 Mar
        • Re: mysqld in an infinite loopSinisa Milivojevic12 Mar
  • Re: mysqld in an infinite loopChristopher Chan11 Mar