Bug #11054 Please add some notes about ledir option for mysqld_multi
Submitted: 2 Jun 2005 22:43 Modified: 21 Jan 2006 18:52
Reporter: Gleb Paharenko Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.4 OS:Linux (Linux)
Assigned to: Paul DuBois CPU Architecture:Any

[2 Jun 2005 22:43] Gleb Paharenko
Description:
Please add some notes about ledir option of mysqld_multi program to 
  http://dev.mysql.com/doc/mysql/en/mysqld-multi.html

It is not clear when we should use from this page of manual, it is mentioned only in the output
of
  mysqld_multi --example

How to repeat:
See above

Suggested fix:
See above
[2 Jun 2005 23:16] Jorge del Conde
Hi!

I'm not sure why would we need ledir in mysqld_multi;  The reason is mysqld_multi expects a 'mysqld' path which is the variable that points to where the server is, and ledir is the path to the directory containing the mysqld program.

Can you please tell me what part isn't clear enough ?

Thanks a lot!
[3 Jun 2005 7:55] Gleb Paharenko
Hi! Every thing is clear after reading the output of mysqld_multi --example. But from the manual
page, it is not clear that we should use this variable (because there're no any notes about ledir). And when we don't use this variable in the [mysqld#] sections mysqld_multi starts all servers using the same binary, even if server versions are different. There is not obvious that
we should launch mysqld_multi with --example option, because parts of configuration file are present at manual. Curious, I was fighting with that problem (the same binary for different instances), until I looked in the source of mysqld_multi and found there the description. However, if you think that it is clear from the manual that we should use ledir if we have mysqld=/path/mysqld_safe , then sorry for wasting your time.
[3 Jun 2005 16:29] Jorge del Conde
Thanks for your bug report.
[21 Jan 2006 18:52] Paul DuBois
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).