[debian-mysql] Bug#778762: closed by Otto Kekäläinen <otto at seravo.fi> (Bug#778762: fixed in mariadb-10.0 10.0.17-1~exp1)
Jan Wagner
waja at cyconet.org
Tue Mar 3 11:36:44 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Sandro,
Am 03.03.15 um 11:43 schrieb Sandro Tosi:
> can you please clarify how
> http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=361e4208eb84121c081d1f1c9affe13284255255
>
>
is supposed to fix the original request:
at first, this bug was origin opened against mysql-server-5.1 if I
remember correctly and I cloned this into mariadb-server.
> """ mysqld_multi is quite interesting so it would be awesome if you
> can provide ab example configuration file, and also an init.d
> script to use instead of the default one.
Usual it maybe common to run just one instance provided by
mysqld_safe. Beside that if you want to have more instances running
you might switch over mysqld_multi.
Anyway you can indeed have running mysqld_safe and mysqld_multi
beside, but this will be much more unusual then running mysqld_multi
standalone itself.
As mysqld_multi can be used in many different scenarios and it is
likely more uncommon than mysqld_safe it doesn`t make sense to provide
a mysqld_multi init script on default. Instead it`s provided a working
example script which can be used by the users itself to setup an
uncommon setup. The "Provides:"-header might needed to be adjusted
anyway, for example if you want to REPLACE the default mysql initscript.
So providing a working example script is a safe way to make life
easier for our users.
> Also, considering shipping a README.mysqld_multi explaining how to
> "convert" your single-mysql-instance machine into a multi-mysqld
> one would be really" """
Don`t get me wrong, it would be very good to have those, but there are
things (not excluding) to consider:
* everybody (you included) are free to provide patches, as it seems
you have looked into it, why not providing one?
* I`m not convinced if those issues you claimed, should be depend on
each other, maybe you should clone the bug again just for the
documentation issue
Cheers, Jan.
P.S. I`m actually not involved into any mysql/mariadb packaging, so
I`m not speaking for any of those teams.
- --
Never write mail to <waja at spamfalle.info>, you have been warned!
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS
PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJU9ZzMAAoJEAxwVXtaBlE+kNMP/3pFrNnYkHXpcgfjh5Cz+Tjp
n6Um0NGlUifE471lN5T7hqqZXcaHJXxbwt0+vTshwUkOAxiCPUKpd6EPbiCNvDaQ
O0DE3sMPY73rb4TiDo7DgccupmWMvNdDZRP4RAQRyNW5gy9QryBhBduSt7eiaWVz
RAAA4QcX30uwI3Gde1hXQrKPyB3a9mrkQRe09Pc7L6ilckfo0hG+z2YbdsepJqFd
Htrca9s4dpneYyfJQdL9prOgwhbES+99wLTObdEs9BWPBJNeg69yeCPFpUVRCba6
+Gbvc3gqHKs6S5C/iyYZmjdAp2VGSnMDx9SlW6XqpXhBHK+tUdG65YkpZvCCJvZI
amWvoAWzAokJAfcO2U/m9ZUZvhPo5Rk68HQIsUyX4FAUpbMXcJCCp5SI4iiC8k5O
UTD3PDROSVXhNRr9crXxaFvplYkXSEpIWlB/umzzQtgZFMPBc/FE7XE3SOTvrEQw
Dm6h3NXuP0dUnKj4GFr1Sj7VSUmOol4ZTQuvhE0W3LWeilFWjBKsfWIo9398G9Cb
CKXST2Q7ThgPY12iwi3nrLH5gHkCjZeAkpt7M17bMXluWDiySV1Ri2A9WAQf7a1H
ek2PHS4ucazdtV1p+DyeqKOmBSI0mM3worBWPecFl2j6k5Qs8ry8fcRLykIuJR9n
sRsrB8k8kJRPmBA8uN03
=W1Dm
-----END PGP SIGNATURE-----
More information about the pkg-mysql-maint
mailing list