Am 06.08.2015 um 13:04 schrieb Guillaume Lefranc:
a) We don't test or support our software on self-built distributions
how 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
* line 4075
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
because all the questions are not relevant
c) You didn't even reply to my questions or give a relevant answer to
any of these
because they where all not useful
d) No one on this mailing list will help you if you adopt such a smug
well, 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 done
e) Suit yourself and have a nice day
On Thu, Aug 6, 2015 at 12:59 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx
Am 06.08.2015 um 12:53 schrieb Guillaume Lefranc:
You don't give any meaningful context at all to solve this
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
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.reindl@xxxxxxxxxxxxx
Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note]
/usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as
why is this now stdout instead mysql logs?
on systemd based distributions that spits now to the global
and finally on machines restarting 2 instances every hour
reasons it annoys
until 10.0.19 or 10.0.20 that was not this way