Comment 2 for bug 551130
Revision history for this message
| Gary B (gar37bic) wrote Re: infinite loop in /etc/init/mysql.conf if mysqld is not running. | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Comparing old and new I don't think there were any changes, although there is a 'log' entry that might not have been original. I do not recall seeing any prompt on this but it's possible that I missed it - the upgrade from 8.04 to 10.0.0.4 was a long process, and a lot of it ran overnight while I was elsewhere. But if the dialog would have required me to click 'OK' or whatever then I don't think that happened. I can attach a copy of my old my.cnf if you want it.
Perhaps this is a minor issue, but two things could be done differently:
* since 'skip_bdb' is deprecated precisely because it's no longer needed, this should at most generate a warning when mysql starts up. It's odd to me that mysql should abort because of a configuration option that is agreeing with it. But I suppose that is really up to the mysql folks.
* IMHO the initctl mysql.conf file (or any automated script) should not have a potential infinite loop like this, especially with no output to tell what is happening. Perhaps this could try to start a certain number of times, then report whatever error messages are coming from mysqladmin and/or mysqld to syslog or dmesg or whatever. Then at least there would be some error output. To get fancy, you could have a double retry loop, spitting out a warning every time the outer loop goes round.
In any case it's just a bad idea to sit and spin forever with no output. I think this is the real 'bug'.