Re: [users@httpd] Why is apache running after doing apachectl -k stop

2012-03-22 Thread Igor Cicimov
Yep, it's up to you how you are going to implement your script. The point is you can't start the server until you confirm that all the threads/children processes have died and the port 80 (or what ever port your apache is running on) is free for the new process to bind to. On Fri, Mar 23, 2012 at

Re: [users@httpd] Why is apache running after doing apachectl -k stop

2012-03-22 Thread Silviu Andrica
Thanks for the replies. I had the impression that apachetcl -k stop will not return until httpd stopped. Cheers, Silviu On Mar 22, 2012, at 23:45 , Daniel Ruggeri wrote: > On 3/22/2012 4:58 PM, Igor Cicimov wrote: >> Thats too fast not all threads can close in just miliseconds you know. >> Add "

Re: [users@httpd] Why is apache running after doing apachectl -k stop

2012-03-22 Thread Daniel Ruggeri
On 3/22/2012 4:58 PM, Igor Cicimov wrote: > Thats too fast not all threads can close in just miliseconds you know. > Add "sleep 5" between stop and start and you should be fine. The only concern with waiting for 5 seconds is that it might not be enough if a request is still finishing up. I often

Re: [users@httpd] Why is apache running after doing apachectl -k stop

2012-03-22 Thread Igor Cicimov
Thats too fast not all threads can close in just miliseconds you know. Add "sleep 5" between stop and start and you should be fine. On Mar 23, 2012 5:20 AM, "silviu andrica" wrote: > Hello, > > I was wondering if running the following commands > sudo /usr/local/apache2.3/bin/apachectl stop > ech