Page 1 of 1

Apache / MySql stop/restart order sensitivity?

PostPosted: 16. October 2006 19:29
by mnemotronic
When I was doing Apache/php/MySql/Tomcat the "old way" (http://mpcon.org/apacheguide/jsp.php), there were order sensitivities when stoping & restarting the various services - especially with Tomcat and Apache. Are there any sensitivities with XAMPP? Does the MySql service need to be restarted before/after Apache, or is it not an issue?

One more thing... XAMPP is just totally friggin kewl. Just thought someone ought to know.

Re: Apache / MySql stop/restart order sensitivity?

PostPosted: 16. October 2006 23:27
by Izzy
mnemotronic wrote:When I was doing Apache/php/MySql/Tomcat the "old way" (http://mpcon.org/apacheguide/jsp.php), there were order sensitivities when stoping & restarting the various services - especially with Tomcat and Apache. Are there any sensitivities with XAMPP? Does the MySql service need to be restarted before/after Apache, or is it not an issue?

One more thing... XAMPP is just totally friggin kewl. Just thought someone ought to know.

I havn't noticed any issues with the start/close order. I sometimes only start mySQL on it's own or Apache on it's own to check configurations etc or to run the Admin... panels.

I often close and open what ever when ever I need them. I can't replicate any issues with the order of things.

Except that if a particular module is needed to display a page, database or send/recieve e-mail etc. then there emits a load groaning and flag waving to let you know you have an issue. ;)

Just to add, if there are any issues with the order of things then I would follow the order that the modules are arranged in the XAMPP Control Panel - xampp\xampp-control.exe ie:
Apache
MySql
FileZilla
Mercury
And TomCat, if used, should be running as a Service and really for convenience so should all the modules that are needed constantly. They can still be stopped and started again as and when required.

Good luck!.