https://bugzilla.novell.com/show_bug.cgi?id=273938 mmarek@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |poeml@novell.com ------- Comment #1 from mmarek@novell.com 2007-05-15 02:10 MST ------- (In reply to comment #0)
1) The datadir is hardcoded (while the init script is not marked noreplace)
It *should* read the config from /etc/my.cnf (see parse_arguments function), but might be that it doesn't work, I'll check ;-)
2) The script waits 10 seconds on startup:
for((i=0; i<50; i++)); do sleep 0.2 test -S $socket && i='' && break done
test -z "$i" || rc_failed
This can be too short, a database with innodb tables of a few gigabytes size can take longer to start up. I would suggest to increase the time to 30 or 60 seconds. And after such a long time, it can probably be assumed that start was _not_ failed, if the socket is still not there, but the mysqld is running.
OK, good point. Just in the update case I really need the socket to run mysql_upgrade.
3) It would be good to wait at stop time, because it can take considerable time to flush buffers to disk after the stop is signalled. (I'm running a large database with a configuration without immediate log flushing for performance reasons)
Also because a restart might fail if the start is attempted before mysqld has quit.
In 10.2 it does wait a minute or so, see bug 223209, do you think the timeout should be higher? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.