MySQL Bugs: #14107: all IM tests fail on QNX

Bug #14107	all IM tests fail on QNX
Submitted:	18 Oct 2005 1:34	Modified:	21 Oct 2005 0:13
Reporter:	Petr Chardin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Instance Manager	Severity:	S3 (Non-critical)
Version:		OS:
Assigned to:	Petr Chardin	CPU Architecture:	Any

Description:
All the IM tests fail on QNX

for instance:

TEST                           RESULT
-------------------------------------------------------

im_life_cycle                  [ fail ]

Errors are (from /home/mysqldev/petr/mysqlcom-5.0.15/mysql-test/var/log/mysqltest-time) :
mysqltest: In included file "./include/im_check_os.inc": At line 1: Could not open connection 'dflt_server_con': Can't connect to local MySQL server through socket '/home/mysqldev/petr/mysqlcom-5.0.15/mysql-test/var/tmp/mysqld_1.sock' (261)
(the last lines may be the most important ones)

Aborting: im_life_cycle failed in default mode. To continue, re-run with '--force'.

This happens since IM doesn't start an instance: IM uses fork() to start an instance, while
fork() doesn't work on QNX in multithreaded apps

How to repeat:
run tests

Suggested fix:
use spawn() instead of fork() to start instances on QNX

on QNX one should use spawn() in threaded environment instead of fork()

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

pushed into 5.0.16