http://qa.mandrakesoft.com/show_bug.cgi?id=1404
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2003-03-09 05:10 -------
Sorry about the default for datadir. I noticed it, but forgot to include it in
my report.
And a second sorry for nitpicking (and somehow hijacking this bug step by step),
but IMHO
datadir=`my_print_defaults mysqld | grep '^--datadir' | cut -d \ -f2-`
has to be
datadir=`my_print_defaults mysqld | grep '^--datadir=' | cut -d= -f2-`
i.e. the key and values are seperated by a "=" sign (The "cut" is the relevant
part. Appending "=" to the "grep" is just some future-safety while I am at it).
>From a production server of mine:
$ my_print_defaults mysqld | grep '^--datadir' | cut -d \ -f2-
--datadir=/var/lib/mysql
$ my_print_defaults mysqld | grep '^--datadir=' | cut -d= -f2-
/var/lib/mysql
So I am not sure why you changed my example "-d=" to "-d \ ". Do I missing
something? (And ignore that in the example above the variable happens to be set
to the default, "/var/lib/mysql").
Aside from that, the changes work fine. Thanks.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: REOPENED
creation_date:
description:
See the mentioned URL. There are some steps to be taken in order to upgrade from
3.23 to 4.0 (4.0 will work on a 3.23 database without those, but not all
features are available). The most notable is the one give in the Summary. Of
course, it is arguable, if all those steps should be automatic, and I would
surely be fine with only printing a message that the user has to run the steps
(maybe cite the mentioned URL).
But I think if neither is done, there will be a lot of questions coming back why
certain features of 4.0 do not work after upgrading.
