mirror of
https://github.com/MariaDB/server.git
synced 2025-01-29 02:05:57 +01:00
2e092583fe
50-mariadb_safe.cnf was only ever intended to be a reference file.
With mariadbd-safe falling into disuse in Debian since systemd became
a service it was assumed this files wasn't used except on a few old
legacy init systems. Its assumed these users will have a configuration
already set.
It is however read by the mariabackup galera-sst script. This forks
off the logger process to write the output to /dev/log, which on a
systemd service the journalctl is reading anyway.
The real harm is on containers where there is now a MariaDB operator
that runs Galera based containers. In containers there is no /dev/log,
so information gets lost.
It would be much more direct just to go straight to stdout/error
like what would happen without this configuration.
Rather than risk the galera-sst scripts moving to the [mariadbd-safe]
group name introduced in
|
||
|---|---|---|
| .. | ||
| innotop | ||
| mariadb.conf.d | ||
| debian-start | ||
| debian-start.inc.sh | ||
| echo_stderr | ||
| mariadb-report | ||
| mariadb-report.1 | ||
| mariadb.cnf | ||
| source_mariadb.py | ||