> and for the Apache and nginx:
>
> [root@srv-rhsoft:~]$ apachectl -t
> AH00526: Syntax error on line 14 of /etc/httpd/conf/httpd-prefork.conf:
> Invalid command 'ddd=dfdfdf', perhaps misspelled or defined by a module
> not included in the server configuration
>
> where is something similar for m
Am 03.09.19 um 11:53 schrieb Benoit Plessis:
>> [root@srv-rhsoft:~]$ apachectl -t
>> AH00526: Syntax error on line 14 of /etc/httpd/conf/httpd-prefork.conf:
>> Invalid command 'ddd=dfdfdf', perhaps misspelled or defined by a module
>> not included in the server configuration
>>
>> where is somet
On 03/09/2019 11:45, Reindl Harald wrote:
> a simple array with all known config options is bloat? have you ever
> written software in any language?
C/C++/perl/shell/java/Coldfusion pick whatever you want...
But i spent more time doing admin and fighting leaks and instability
> and for the Apac
Am 03.09.19 um 11:38 schrieb Benoit Plessis:
> On 03/09/2019 11:25, Reindl Harald wrote:
>> when i *explicit disable* some bloatware crap it's missing exitence is
>> not a hard error
> Well, so you want to add some "bloat" to a software to handle deprecated
> bloated "crap", are you sure to thin
On 03/09/2019 11:31, Sergei Golubchik wrote:
> Hi, Benoit!
>
> [..]
>
> Note, that his use case is an option that was explicitly set to its
> default value in my.cnf, and in 10.3 was removed in the server (so the
> default value became hard-coded behavior and not configurable anymore).
>
> That is,
On 03/09/2019 11:25, Reindl Harald wrote:
> yes
Yet you continue using an inappropriate tone/wording just below ...
maybe you could take a bit of your own advice don't you think ?
> "-DPLUGIN_PERFSCHEMA=NO" is the same as "performance-schema=0" is doing
> the same while "performance-schema=0" on
Hi, Benoit!
On Sep 03, Benoit Plessis wrote:
>
> As for your 'kind suggestion' of handling deprecated/unknown option i
> personnally strongly disagree, some of mysql/mariadb options have real
> impact and "physical" consequences on the database, preventing it to
> start because of setting not han
Am 03.09.19 um 09:50 schrieb Benoit Plessis:
>> Am 02.09.19 um 19:38 schrieb Faustin Lammler:
>>> I am truly sorry by the issue you are facing, but giving us *in
>>> your first post* the version and the OS would have been more
>>> productive IMHO
>>
>> don't get me wrong *but* i find it insulting
>
>
> Am 02.09.19 um 19:38 schrieb Faustin Lammler:
> > I am truly sorry by the issue you are facing, but giving us *in
> > your first post* the version and the OS would have been more
> > productive IMHO
>
> don't get me wrong *but* i find it insulting when someone accueses me
> that i jump from s
Hi, Marko!
On Sep 02, Marko Mäkelä wrote:
> On Mon, Sep 2, 2019 at 8:48 PM Reindl Harald wrote:
> > and yes, i assumed that a core developer other than you would look
> > at that startup log, came to the conslusion "indeed, no warning
> > there" and while read the few lines "indeed, the latest 10
Am 02.09.19 um 20:20 schrieb Marko Mäkelä:
> On Mon, Sep 2, 2019 at 8:48 PM Reindl Harald wrote:
>> and yes, i assumed that a core developer other than you would look at
>> that startup log, came to the conslusion "indeed, no warning there"
>> and while read the few lines "indeed, the latest 10.
On Mon, Sep 2, 2019 at 8:48 PM Reindl Harald wrote:
> and yes, i assumed that a core developer other than you would look at
> that startup log, came to the conslusion "indeed, no warning there"
> and while read the few lines "indeed, the latest 10.2 version"
You are right that a warning should be
Hi Faustin,
On Mon, Sep 2, 2019 at 7:05 PM Faustin Lammler wrote:
[snip]
> Anyway, there maybe some useful information here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920608
>
> Marko, I believe we can expect these kinds of deprecation with people
> upgrading from Debian Stretch to Bust
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 02.09.19 um 19:38 schrieb Faustin Lammler:
> I am truly sorry by the issue you are facing, but giving us *in
> your first post* the version and the OS would have been more
> productive IMHO
don't get me wrong *but* i find it insulting when some
Reindl Harald ,
02/09/2019 – 18:12:53 (+0200):
> > Maybe giving us the version you are upgrading from would have been
> > a better starting point.
>
> maybe read what i wrote instead cut down my post by the first line
> would be a god start too or simply shut up when you are too lazy read
> a log
Am 02.09.19 um 19:21 schrieb Sergei Golubchik:
> On Sep 02, Reindl Harald wrote:
>> Am 02.09.19 um 17:09 schrieb Marko Mäkelä:
>>> On Mon, Sep 2, 2019 at 5:43 PM Reindl Harald wrote:
unknown variable 'innodb_support_xa=1'
would you funny guys consider things like deperectaion warn
Hi, Reindl!
On Sep 02, Reindl Harald wrote:
> Am 02.09.19 um 17:09 schrieb Marko Mäkelä:
> > On Mon, Sep 2, 2019 at 5:43 PM Reindl Harald wrote:
> >> unknown variable 'innodb_support_xa=1'
> >>
> >> would you funny guys consider things like deperectaion warnings in
> >> previous releases
> >
> >
Am 02.09.19 um 18:05 schrieb Faustin Lammler:
> After reading the recent thread on systemd devel ML (/etc/fstab
> obsolete?) I kind of find your tone a bit inappropriate. May I
> suggest you to try to start by applying your advice to yourself.
that stupid behavior of mariadb was pointed out oft
Hi Reindl,
After reading the recent thread on systemd devel ML (/etc/fstab
obsolete?) I kind of find your tone a bit inappropriate. May I suggest
you to try to start by applying your advice to yourself.
This is clearly not a
> good start for a discussion
https://lists.freedesktop.org/archives/sys
Am 02.09.19 um 17:18 schrieb Benoit Plessis:
> On 02/09/2019 17:13, Reindl Harald wrote:
>>> A deprecation warning was added in the MariaDB Server 10.2.2, well
>>> before it was Generally Available.
>>> That said, maybe there is a nontrivial amount of users who skipped the
>>> 10.2 release and u
On 02/09/2019 17:13, Reindl Harald wrote:
>> A deprecation warning was added in the MariaDB Server 10.2.2, well
>> before it was Generally Available.
>> That said, maybe there is a nontrivial amount of users who skipped the
>> 10.2 release and upgraded straight from 10.1 to 10.3.
> come on and show
Am 02.09.19 um 17:09 schrieb Marko Mäkelä:
> On Mon, Sep 2, 2019 at 5:43 PM Reindl Harald wrote:
>> unknown variable 'innodb_support_xa=1'
>>
>> would you funny guys consider things like deperectaion warnings in
>> previous releases
>
> A deprecation warning was added in the MariaDB Server 10.2
On Mon, Sep 2, 2019 at 5:43 PM Reindl Harald wrote:
> unknown variable 'innodb_support_xa=1'
>
> would you funny guys consider things like deperectaion warnings in
> previous releases
A deprecation warning was added in the MariaDB Server 10.2.2, well
before it was Generally Available.
That said,
unknown variable 'innodb_support_xa=1'
would you funny guys consider things like deperectaion warnings in
previous releases or at least offer an option to change all these
fucking "i don't know a option because it was removed or you did not
compile something in and hence i refuse to start the serv
24 matches
Mail list logo
