I'm not sure what the real value of this new concurrent mysql server check is, as the use case is usually handled automatically. People who have a preexisting MySQL server running and don't know it will likely have both mysql servers configured to run on the default port of 3306 - in which case starting up XAMPP's MySQL server will fail-safe as expected anyway.
Well, in the meantime I can employ one these two workarounds
- As described in the post, Control Panel Refuse, I can disable all startup tests by editing the 'RunStartTests' setting by invoking:
- Code: Select all
sudo open '/Applications/XAMPP/XAMPP Control.app/Contents/PlugIns/MySQL.plugin/Contents/Info.plist'
... This has the downside of disabling ALL startup tests, which I don't like.
- I can kill my other MySQL server, then start XAMPP's, then start the other again. Annoying, but it works.