summaryrefslogtreecommitdiff
path: root/sql/share/czech
diff options
context:
space:
mode:
authorunknown <guilhem@mysql.com>2003-12-16 21:52:11 +0100
committerunknown <guilhem@mysql.com>2003-12-16 21:52:11 +0100
commit4790088f46493e0414a14f066c241fdd9c2836c0 (patch)
tree761a7d8ce85eb6a5b4c8fa73435f36a014e25ebe /sql/share/czech
parentb26fd7b9222705e0483e73b8c9e0faca449561ab (diff)
downloadmariadb-git-4790088f46493e0414a14f066c241fdd9c2836c0.tar.gz
Fix for BUG#2121 "Inadequate message "check permissions on master.info"":
more general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). The perfect fix would be to report the exact error to the client (instead of pointing the client to the error log); this is a bit of work so it's more a development task: WL#1088 "Move all hardcoded messages of replication to share/errmsg.txt". I was not able to modify the errmsg.txt in these sql/ subdirectories: danish dutch german italian portuguese russian spanish swedish ukrainian mysql-test/r/rpl_rotate_logs.result: result update sql/share/czech/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/english/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/estonian/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/french/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/greek/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/hungarian/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/japanese/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/korean/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/norwegian-ny/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/norwegian/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/polish/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/romanian/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). sql/share/slovak/errmsg.txt: More general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions).
Diffstat (limited to 'sql/share/czech')
-rw-r--r--sql/share/czech/errmsg.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/share/czech/errmsg.txt b/sql/share/czech/errmsg.txt
index 72a593cf5f7..069ee4540a3 100644
--- a/sql/share/czech/errmsg.txt
+++ b/sql/share/czech/errmsg.txt
@@ -211,7 +211,7 @@
"This operation cannot be performed with a running slave, run SLAVE STOP first",
"This operation requires a running slave, configure slave and do SLAVE START",
"The server is not configured as slave, fix in config file or with CHANGE MASTER TO",
-"Could not initialize master info structure, check permisions on master.info",
+"Could not initialize master info structure, more error messages can be found in the MySQL error log",
"Could not create slave thread, check system resources",
"User %-.64s has already more than 'max_user_connections' active connections",
"You may only use constant expressions with SET",