From: Noel Butler Date: December 21 2010 7:03am Subject: Re: Autostart not working for me in 5.5.8 version List-Archive: http://lists.mysql.com/mysql/223858 Message-Id: <1292915036.28188.12.camel@tardis> MIME-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-NEB0I4Vip7FbNw7p5n7l" --=-NEB0I4Vip7FbNw7p5n7l Content-Type: multipart/related; type="multipart/alternative"; boundary="=-Kzt/y1K17qEBugiBJqjh" --=-Kzt/y1K17qEBugiBJqjh Content-Type: multipart/alternative; boundary="=-Qk1QjPdtCJ+hlvT7Faj6" --=-Qk1QjPdtCJ+hlvT7Faj6 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable Hi Joerg, On Mon, 2010-12-20 at 18:59 +0100, Joerg Bruehe wrote: > Hi Noel, all! >=20 >=20 > Noel Butler wrote: > > On Thu, 2010-12-16 at 10:08 -0300, Alejandro Bednarik wrote: > >> You are right. In previous version init script have a default value, n= ow is > >> empty. > >> > >> mysql 5.1..53 - basedir=3D/usr/local/mysql > >> > >> mysql-5.5.8 - basedir=3D. > >> > >=20 > >=20 > > /me ponders at who the IDIOT is that decided that cmake is the way of > > mysql now. > > I mean WTF... >=20 > It was the ones who realized that two different build mechanisms > (autotools for Unix, cmake for Windows) will always cause divergence, > when one is maintained with a change and the other isn't. >=20 > Being database people, we know the importance of consistency ;) >=20 I can tell its done by windowsy people, it has pretty colours :) seriously though , it's almost as bad as trying to figure out what to give postifx hehe And in the real world, many sysadmins have to build the database servers for the database admins, I've made my opinion known about cmake so I'll leave my cursing at that. > >=20 > > /me sticks with 5.1 >=20 > Do as you like, but realize that 5.1 won't see major development in the > future and will be put on "extended support only" in due time. >=20 For what we use it for, it's likely fine, (user auth/radius/web/mail etc etc etc) nothing complex. > So if anybody encounters differences between 5.1 and 5.5 in such > settings which aren't documented (=3D by intention, or unavoidable), > please file bugs to get them fixed. >=20 Well, the documentation could be a little more in depth, if you remove method A, and if method B is completely compatible, then there must be detailed information, it is not very good for time management to spend hours looking over the website, yes forge.mysql.com has a handy reference, but the bit about replacing, for instance plugins=3Dmax, it is not clear what we need to include, we know what is default, and some examples of to add given the example given, but no reference to the max server, without time consuming research to see what plugins=3Dmax includes, compare, then find equivalent DINSTALL_blah=3D1's to add, I think it is a backwards step, and you're likely to see more cussing as more go to upgrade. Nice thing though, my original my.cnf didnt cause it to bail out upon restart, however I only installed it on one very light use server. want to lay with it a bit before it goes on anything too serious. Cheers --=-Qk1QjPdtCJ+hlvT7Faj6 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Joerg,

On Mon, 2010-12-20 at 18:59 +0100, Joerg Bruehe wrote:

Hi Noel, all!

Noel Butler wrote:
> On Thu, 2010-12-16 at 10:08 -0300, Alejandro Bednarik wrote:
>> You are right. In previous version init script have a default valu=
e, now is
>> empty.
>>
>> mysql 5.1..53   -   basedir=3D/usr/local/mysql
>>
>> mysql-5.5.8  -   basedir=3D.
>>
>=20
>=20
> /me ponders at who the IDIOT is that decided that cmake is the way of
> mysql now.
>  I mean WTF...

It was the ones who realized that two different build mechanisms
(autotools for Unix, cmake for Windows) will always cause divergence,
when one is maintained with a change and the other isn't.

Being database people, we know the importance of consistency  ;)

I can tell its done by windowsy people, it has pretty colours 3D":)"

seriously though , it's almost as bad as trying to figure out what to give = postifx hehe
And in the real world, many sysadmins have to build the database servers fo= r the database admins, I've made my opinion known about cmake so I'll leave= my cursing at that.

>=20
> /me sticks with 5.1

Do as you like, but realize that 5.1 won't see major development in the
future and will be put on "extended support only" in due time.

For what we use it for, it's likely fine, (user auth/radius/web/mail etc et= c etc) nothing complex.

So if anybody encounters differences between 5.1 and 5.5 in such
settings which aren't documented (=3D by intention, or unavoidable),
please file bugs to get them fixed.

Well, the documentation could be a little more in depth, if you remove meth= od A, and if method B is completely compatible, then there must be detailed= information, it is not very good for time management to spend hours lookin= g over the website, yes forge.mysql.com has a handy reference, but the bit = about replacing, for instance plugins=3Dmax, it is not clear what we = need to include, we know what is default, and some examples of to add given= the example given, but no reference to the max server, without time consum= ing research to see what plugins=3Dmax includes, compare, then find equival= ent DINSTALL_blah=3D1's to add, I think it is a backwards step, and you're = likely to see more cussing as more go to upgrade.

Nice thing though, my original my.cnf didnt cause it to bail out upon resta= rt, however I only installed it on one very light use server.
want to lay with it a bit before it goes on anything too serious.

Cheers

--=-Qk1QjPdtCJ+hlvT7Faj6-- --=-Kzt/y1K17qEBugiBJqjh Content-ID: <1292914393.28188.0.camel@tardis> Content-Disposition: attachment; filename="face-smile.png" Content-Type: image/png; name="face-smile.png" Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAAB3RJ TUUH1wgOER8RqU5d7gAAAwtJREFUOI1lk01oXGUYhZ/73Ts/sWPiT8YE2ti6SF00jDWBaBWLuhFB QgUNQsFdCair2pVSBV3YGkNWDVjcqKlIaG2sLf5EUBqTBkqjTFMi2Px2ojOTpJnMZHLnfvd+3+si VKR5V2dxOBx4z+Nw1419QZty3R5EdYmJmgEcpfIgF6zYT59+nan/+5074sYQ8XIQG/ASjYdbDxyP px58Rql4M0hIFMxQKf5sb149pY1eOdOQ4I193ej/AoaGcFt07PKufUc6dmY+ShBOI+FfQAB4ID5C CieeYWHy3SA/c/FaLsHB7m4MABNfxfpvTfb4YkpiNi+K1X+K2EDEhiKmIhIVxNauil55R6LNUZkZ e96fGKQfwBn7jN3xhqZsx8tT9aInUYlOTvSeYrlYoK/3fcRWOdk7wHJxiY8/eBZdPo/X8BZ/XHql HG5UM0olvaOtT7yXIprF8fYALmfPfcPwt5dANNgyZ8+PMPzdOJh/wOQx/ii7M6+mSHJU4ahDqfRz SqJ5cGIgNR5t3Uv7/gxifbDr7H0kxeNtOxB9A3Aw/jip9EHlCIc8G0VNKpZGdBGiHOI+xODnJ0FC xK6AKfDl6ZcgmkOiRcBg9QLJB1qwliYPAIkQKUM4DbYETt1WfSmDWQa7BraKNTXEBohoQADwHNct mGD+YSUKMXkc8cFJbhlsFbFrYFYRW8KaDazxQaUJ/XmUoqAEM1wufG/xdkK0xOTICW4v/YKuTmP0 AjbMEdYWWc3Pcv1KFmMquHWdVJYvW3EY3nrjvfdl27t+qpfKaW5X2slN9VEtLWEiDYDredxT38iu treJywB16Q/J/nikHG5UM1tDGlT9c1de9CN/XMK1T8TUrok1ayJWi9hAbLQqYXVUqn+/KUHpa5n5 7anNO0PyABbj9pi9+UOniNPR8tjxRLgxgvF/xeg5xAY4bhq37gDejhe4db2vVpwb/z2X4Ng2mNZr DLjx+w/v2f9aPNX4pIolW0AsoT9LZWXCLmTPaaPXzzQk74JpG84OPQJdWJoBUOQduGCFbTj/C8H3 uN+XWOgHAAAAAElFTkSuQmCC --=-Kzt/y1K17qEBugiBJqjh-- --=-NEB0I4Vip7FbNw7p5n7l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAABAgAGBQJNEFFXAAoJECg/hgl/0DbHCE4H/R+0ADvOR7NSPLbHTFQUy7xe xbXxkwUYVzGx9ipR0fv9wmKptoetmQmqvsp7t9NTGvQsw7plUsa4dqDPvxQYnPBE LLp+ypkkFOX04mk+3YaqG84TE1J9+6PoA9BdMjnkfLtvVp3qHz69zjspxt9T/qad 4wKCzZx/bLmYT1DbbdwFgDEBlmjFDxWP0+3xjQW74JLM2tag0N1gzCNcN0+sPn01 LjXxRZXA8ZwGm6gRhOLAEUhtIvf7iIp7KfbKMNPTc0TGc5gFWZ7ZZ0yC9Cp/9ris sTLAuPKEzZ/kGqhkF80ncxEahV3JvHSKeUPgYTIDk4WD5SCMMbTkt5fwwf9kc+k= =xlh8 -----END PGP SIGNATURE----- --=-NEB0I4Vip7FbNw7p5n7l--