Bug #46242 disk data - intialLogfilegroup in config.ini is broken

Description:
[ndbd default]
...
InitialLogFileGroup = name=lg; undobuffer_size=2M; undo1.dat:1G;
..

seems to be parsed as:
InitalLogfileGroup: name=lg; undobuffer_size=2M; undo1.dat:1G;

hmm spelling mistake?

Time: Thursday 16 July 2009 - 22:47:38
Status: Permanent error, external action needed
Message: Invalid configuration received from Management Server (Configuration error)
Error: 2350
Error data: Unable to parse InitalLogfileGroup: name=lg; undobuffer_size=2M; undo1.dat:1G;
Error object: NDBCNTR (Line: 417) 0x0000000e
Program: /usr/local/mysql//mysql/bin//ndbd
Pid: 14148
Trace: /data1/mysqlcluster//ndb_3_trace.log.3
Version: mysql-5.1.34 ndb-7.0.6
***EOM***

How to repeat:
add 
InitialLogFileGroup = name=lg; undobuffer_size=2M; undo1.dat:1G;
to config.ini

please also theck 
InitialTablespace... if that is also has a spelling mistake.

Suggested fix:
-

problem was
1) stray ";" at end of config parameter
2) spelling error in *error message*

patch
1) allows stray ";" at *end* of config value
2) fixes spelling error in error message

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/79873

2958 Jonas Oreland	2009-08-03
      ndb - bug#46242
        1) allow stray ";" at end of config values
        2) fix spelling in error message

Pushed into 5.1.35-ndb-6.3.26 (revid:jonas@mysql.com-20090803130332-pesbastqnj76b1is) (version source revid:jonas@mysql.com-20090803130332-pesbastqnj76b1is) (merge vers: 5.1.35-ndb-6.3.26) (pib:11)

Pushed into 5.1.35-ndb-7.0.7 (revid:jonas@mysql.com-20090803153854-un8jv9y2md8k221t) (version source revid:jonas@mysql.com-20090803153854-un8jv9y2md8k221t) (merge vers: 5.1.35-ndb-7.0.7) (pib:11)

also pushed into 6.2.19

Bugfix documented in the NDB-6.2.19, 6.3.26, and 7.0.7 changelogs as follows:

        Ending a line in the config.ini file with an extra semicolon
        character (;) caused reading the file to fail with a parsing
        error.