http://tech-recipes.disqus.com/Cookbook of Tech TutorialsenTue, 11 Nov 2003 09:23:56 -0000http://www.tech-recipes.com/rx/110/restart-apache-without-closing-open-connections/#comment-2766935<p>Failing to find <strong>apachectl</strong>, one could just find the PID of the parent httpd process and send a -USR1 signal to it.</p><p>For example:</p><p><code><br>$ ps -ef | grep httpd<br>root 17723 1 0 Sep23 ? 00:00:01 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3666 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3667 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3668 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3669 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3670 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3671 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3672 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br>apache 3673 17723 0 Nov09 ? 00:00:00 /usr/sbin/httpd -DHAVE_ACCESS -D<br><br>$ kill -USR1 17723<br></code></p><p>a -USR1 signal will cause any new children to run with a new configuration, but leave the current children running as-is. A -HUP signal will kill off all current children and cause new requests to be serviced under the new configuration.</p><p>Of course, one could be a little more sophisticated:</p><p><code><br><br>$ ps -ef | grep httpd | grep root | awk '{print $2}' | xargs kill -HUP<br><br></code></p><p>That said, apachectl is a lot cleaner.</p>bofh468Tue, 11 Nov 2003 09:23:56 -0000