Am 06.08.2015 um 13:24 schrieb Jean Weisbuch:
I will try not to feed the troll.
do you really think it's trolling to have zero understanding for useless questions?
Here is the commit that added this message : https://github.com/MariaDB/server/commit/ddd275bde7a8edb64449761989d4d472739b3d2a#diff-e7d51f293adc9257284fbdec858056df
"we log a server version information just after we prepare server_version string and logging is initialized"
but it is *not* logged, it goes to stdout and hence on systems which does not forward stdout to syslog they are not visible at all and in case of troubles you typically look in the mysqld log
that message is at the wrong place - period
Le 06/08/2015 13:11, Reindl Harald a écrit :Am 06.08.2015 um 13:04 schrieb Guillaume Lefranc:a) We don't test or support our software on self-built distributionshow does that matter at all? the codeline below is distribution and build agnostic that log message is echo'ed to stdout [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 * mysqld.cc * line 4075 if (!opt_help) sql_print_information("%s (mysqld %s) starting as process %lu ...", my_progname, server_version, (ulong) getpid());b) I am not gifted with prescience to respond to such questions as "same as before"because all the questions are not relevantc) You didn't even reply to my questions or give a relevant answer to any of thesebecause they where all not usefuld) No one on this mailing list will help you if you adopt such a smug tonewell, you sounded like a random user asking useless questions well, one more message to drop in rsyslog.conf i really ask myself why report anything at all and waste my time instead just burry all log flooding and be donee) Suit yourself and have a nice dayyou tooOn Thu, Aug 6, 2015 at 12:59 PM, Reindl Harald <h.rei...@thelounge.net <mailto:h.rei...@thelounge.net>> wrote: Am 06.08.2015 um 12:53 schrieb Guillaume Lefranc: You don't give any meaningful context at all to solve this issue. really? what is so hard to understand in "why is only this one message not written to the mysqld log but goes ot stdout with recent releases?" if you know what stdout means that's pretty clear if you don't know you are hardly a developer who could change it What's the distribution you using? self built as all the years befor What commands do you use to start the same as always /usr/libexec/mysqld --defaults-file=/etc/my.cnf --pid-file=/run/mysqld/mysqld.pid mariadb? surely, did you see the mysqld 10.0.20-MariaDB? Where do you see this message? in /var/log/messages as said *because* it's thrown to stdout which is catched by systemd-journald while anything else goes to "log-error" from my.cnf 2015-08-06 12:27 GMT+02:00 Reindl Harald <h.rei...@thelounge.net <mailto:h.rei...@thelounge.net> <mailto:h.rei...@thelounge.net <mailto:h.rei...@thelounge.net>>>: Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp