<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Restarting Apache/httpd</title>
	<atom:link href="http://www.skillett.com/technology/computers/software/linux/restarting-apachehttpd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.skillett.com/technology/computers/software/linux/restarting-apachehttpd/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=restarting-apachehttpd</link>
	<description>Keiron&#039;s daily take on life, the internet and the world around us!</description>
	<lastBuildDate>Sun, 22 Jan 2012 17:23:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: adrianbanks</title>
		<link>http://www.skillett.com/technology/computers/software/linux/restarting-apachehttpd/comment-page-1/#comment-183</link>
		<dc:creator>adrianbanks</dc:creator>
		<pubDate>Fri, 02 Mar 2007 20:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.skillett.com/index.php/395/restarting-apachehttpd/#comment-183</guid>
		<description>When I used to administer an apache server, I always restarted using the graceful command.

As I remember (it was a few years ago), the graceful restart stops the current request handler from accepting new connections, but allows it to deal with existing requests. Once all of its request have been dealt with it is killed off. Whilst this is happenning, a new request handler is made to deal with new requests, which then remains as the sole request handler when the other one is killed off. Quite a nice feature.</description>
		<content:encoded><![CDATA[<p>When I used to administer an apache server, I always restarted using the graceful command.</p>
<p>As I remember (it was a few years ago), the graceful restart stops the current request handler from accepting new connections, but allows it to deal with existing requests. Once all of its request have been dealt with it is killed off. Whilst this is happenning, a new request handler is made to deal with new requests, which then remains as the sole request handler when the other one is killed off. Quite a nice feature.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

