mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
106e590086
When fixing the 27072 bug, the shell snippets running before/after a RPM upgrade got expanded to look at files in the data directory and at the PID file. In this expansion, the standard locations were used. There are users who configure their installations to use non-standard locations for the data directory, the PID file, and other objects. For these users, the fix of 27072 did not work. As a result, the fact that a server was running at upgrade start was not noticed, and the new server was not started after the upgrade. With this patch, the shell snippets now try to get these locations from "my_print_defaults" before falling back to the defaults. Now, the fact that the old server is running is again noticed (even with non-standard locations), and the new server is started. Also, the upgrade log is written to the correct data directory. support-files/mysql.spec.sh: See the global comment for the purpose of this change. In tests on SuSE 11, it was found necessary to use the full path name of "my_print_defaults", it seems $PATH die not include "/usr/bin". |
||
|---|---|---|
| .. | ||
| MacOSX | ||
| RHEL4-SElinux | ||
| .cvsignore | ||
| binary-configure.sh | ||
| build-tags | ||
| compiler_warnings.supp | ||
| config.huge.ini.sh | ||
| config.medium.ini.sh | ||
| config.small.ini.sh | ||
| magic | ||
| Makefile.am | ||
| my-huge.cnf.sh | ||
| my-innodb-heavy-4G.cnf.sh | ||
| my-large.cnf.sh | ||
| my-medium.cnf.sh | ||
| my-small.cnf.sh | ||
| mysql-log-rotate.sh | ||
| mysql-multi.server.sh | ||
| MySQL-shared-compat.spec.sh | ||
| mysql.m4 | ||
| mysql.server-sys5.sh | ||
| mysql.server.sh | ||
| mysql.spec.sh | ||
| mysqld_multi.server.sh | ||
| ndb-config-2-node.ini.sh | ||