maria-discuss team mailing list archive

[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 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.reindl@xxxxxxxxxxxxx
> <mailto: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 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

Attachment: signature.asc
Description: OpenPGP digital signature