Summary: | mysql init script returns with "eend $?" while mysqld is not ready to accept connections | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Stoll <technoworx> |
Component: | [OLD] Server | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ginsu.squirrel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | etc_init.d_mysql.patch |
Description
Alexander Stoll
2005-04-26 02:29:32 UTC
This patch should do the work, it's based on the creation of MySQL socket file. The function "mysql_get_socket" skip some checks because it's called after checkconfig. Created attachment 57280 [details, diff]
etc_init.d_mysql.patch
fixed in 4.0.24-r2 and 4.1.12 I still get !! on 4.1.12. @Ron try to mannually copy "/usr/portage/dev-db/mysql/files/mysql-4.0.24-r2.rc6" in "/etc/init.d/mysql" . Probably this last one is not updated The diff turns up nothing. It got updated properly. I noticed right away it was different, it says Starting mysqld (/etc/mysql/my.cnf) when i start it. Well seeing as no one else seems to be having problems with this, I figured I'd try to understnad why it's not working on my box. My first problem seems to be with the stop() routine. If I run /etc/init.d/mysql stop it returns within less then a second, but mysql is still running afterward. But if I manually run the start-stop-daemon command it takes about 2 seconds and mysql is properly killed afterwards. My second problem is with start(). retstatus is set to $? right after the command is run, and it is 1. But I dont see anywhere where it gets set to 0 after the script has determined mysql has actually started. |