MySQL Bugs: #17411: cannot have path longer than 128 characters

Bug #17411	cannot have path longer than 128 characters
Submitted:	15 Feb 2006 4:59	Modified:	16 Feb 2006 13:17
Reporter:	Stewart Smith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.0.19bk	OS:	Any (all)
Assigned to:	Stewart Smith	CPU Architecture:	Any

Description:
long paths are silently truncated.

This is hit on pushbuild where the cluster log file name could be truncated to:

/data0/pushbuild/mysql-5.0/push-kent@mysql.com-20060210195910.info/mysql-5.0.19-standard/mysql-test/var/ndbcluster-1005

too bad if there was a file there that you actually wanted

How to repeat:
put a long pathname in config.ini (or have a long name clone and try mysql-test-run)

Suggested fix:
use PATH_MAX (specified by POSIX to be longest valid path on host OS).

If this blows up on win32 then we can just #ifndef PATH_MAX when we get to the stage of looking after ndb on win32 again

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2632

pushed to 5.0.19 and 5.1.7

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:

Documented in 5.0.19 and 5.1.7 changelogs. Closed.