Blame SOURCES/mariadb-recoverpath.patch

9c9e62
Upstream changed location of the temporary file in the wsrep_recover_position
9c9e62
function, which causes issues on RHEL-6, because mysqld_safe is not expected
9c9e62
to play with files in /tmp, and SELinux started to complain.
9c9e62
9c9e62
Changing the location of the temporary files to the datadir means practically
9c9e62
reverting part of the upstream commit
9c9e62
https://github.com/MariaDB/server/commit/bb7a70c9551c1756b1d1736ca4f6a0a965795873
9c9e62
9c9e62
Upstream issue: https://jira.mariadb.org/browse/MDEV-10767
9c9e62
9c9e62
diff -up mariadb-10.1.29/scripts/mysqld_safe.sh.recoverpath mariadb-10.1.29/scripts/mysqld_safe.sh
9c9e62
--- mariadb-10.1.29/scripts/mysqld_safe.sh.recoverpath	2017-11-23 10:48:37.538678722 +0100
9c9e62
+++ mariadb-10.1.29/scripts/mysqld_safe.sh	2017-11-23 10:50:48.134585794 +0100
9c9e62
@@ -246,7 +246,7 @@ wsrep_recover_position() {
9c9e62
   local euid=$(id -u)
9c9e62
   local ret=0
9c9e62
 
9c9e62
-  local wr_logfile=$(mktemp /tmp/wsrep_recovery.XXXXXX)
9c9e62
+  local wr_logfile=$(mktemp $DATADIR/wsrep_recovery.XXXXXX)
9c9e62
 
9c9e62
   # safety checks
9c9e62
   if [ -z $wr_logfile ]; then