Use lowercase for "Too long dbname" test as it will be put ot lower on some platforms and we don't wan't to test that.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.0-maint

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mtr_vs_config/my50-mtr_vs_config

Visual Studio builds each configuration in a different sub-directory.  Only the sub-
directories for release and debug are currently searched.

into  kpdesk.mysql.com:/home/thek/dev/mysql-5.0-maint

- 'false' not defined in C, use FALSE instead.

into  mysql.com:/usr/home/ram/work/bug22913/my50-bug22913

into  mysql.com:/usr/home/ram/work/bug22913/my50-bug22913

We don't check for errors that may occur during data printing.

into  bodhi.local:/opt/local/work/mysql-5.0-runtime-merge

into  bodhi.local:/opt/local/work/mysql-5.0-runtime-merge

into  bodhi.local:/opt/local/work/mysql-4.1-runtime

into  kpdesk.mysql.com:/home/thek/dev/mysql-5.0-maint

  bug#21052

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  shellback.(none):/home/msvensson/mysql/mysql-5.0-maint

into  mockturtle.local:/home/dlenev/src/mysql-5.0-hash-2

Use lazy initialization for Query_tables_list::sroutines hash.
This step should significantly decrease amount of memory consumed
by stored routines as we no longer will allocate chunk of memory
required for this HASH for each statement in routine.

into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint

into  shellback.(none):/home/msvensson/mysql/mysql-5.0-maint

 - Only read *.pid
 - Only allow it to contain a number 

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb

  remove timeing dependant part of test

into  mysql.com:/usr/home/ram/work/bug22723/my50-bug22723

- Because my_seek actually is capable of returning an error code we should
  exploit that in the best possible way.
- There might be kernel errors or other errors we can't predict and capturing
  the return value of all system calls gives us better understanding of
  possible errors.

into  mysql.com:/usr/home/ram/work/bug23412/my41-bug23412

into  mysql.com:/usr/home/ram/work/bug23412/my50-bug23412

into  mysql.com:/usr/home/ram/work/bug23412/my50-bug23412

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug21915

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21915

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug21915

If the user has specified --max-connections=N or --table-open-cache=M
options to the server, a warning could be given that some values were
recalculated, and table-open-cache could be assigned greater value.

Note that both warning and increase of table-open-cache were totally
harmless.

This patch fixes recalculation code to ensure that table-open-cache will
be never increased automatically and that a warning will be given only if
some values had to be decreased due to operating system limits.

No test case is provided because we neither can't predict nor control
operating system limits for maximal number of open files.

into  shellback.(none):/home/msvensson/mysql/mysql-4.1-maint

 - Wait in loop with small sleep until tables has been renamed