<?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: How To Deal With Huge Apache Web Server Log Files</title>
	<atom:link href="http://www.ghacks.net/2008/10/01/how-to-deal-with-huge-apache-web-server-log-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghacks.net/2008/10/01/how-to-deal-with-huge-apache-web-server-log-files/</link>
	<description>A technology blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description>
	<lastBuildDate>Tue, 10 Nov 2009 03:01:23 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dotan Cohen</title>
		<link>http://www.ghacks.net/2008/10/01/how-to-deal-with-huge-apache-web-server-log-files/#comment-495481</link>
		<dc:creator>Dotan Cohen</dc:creator>
		<pubDate>Thu, 02 Oct 2008 08:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=7325#comment-495481</guid>
		<description>&gt; It is important to note that you might need to stop
&gt; the Apache web server for the operation to succeed
&gt; because the compression utility will stop if files
&gt; get changed during procession.

How about copying the logfile to another location before compressing? This will of course only be practical if the logile is less than half of your available space, though if that is _not_ your situation then you are in trouble!

This is why logfiles are usually stored in /var and why /var is recommended to be on it&#039;s own partition. When there is a traffic spike Apache logs can grow very fast, and when there are other problems (hardware failure, bad software update, breach) other logfiles can grow very quickly as well. If they are on their own partition they won&#039;t take down the server.</description>
		<content:encoded><![CDATA[<p>&gt; It is important to note that you might need to stop<br />
&gt; the Apache web server for the operation to succeed<br />
&gt; because the compression utility will stop if files<br />
&gt; get changed during procession.</p>
<p>How about copying the logfile to another location before compressing? This will of course only be practical if the logile is less than half of your available space, though if that is _not_ your situation then you are in trouble!</p>
<p>This is why logfiles are usually stored in /var and why /var is recommended to be on it&#8217;s own partition. When there is a traffic spike Apache logs can grow very fast, and when there are other problems (hardware failure, bad software update, breach) other logfiles can grow very quickly as well. If they are on their own partition they won&#8217;t take down the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.ghacks.net/2008/10/01/how-to-deal-with-huge-apache-web-server-log-files/#comment-494197</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 01 Oct 2008 09:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=7325#comment-494197</guid>
		<description>Yes logrotate is a very good option which would have saved me the hassle of dealing with a 45 Gigabyte log file in first place.</description>
		<content:encoded><![CDATA[<p>Yes logrotate is a very good option which would have saved me the hassle of dealing with a 45 Gigabyte log file in first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pga</title>
		<link>http://www.ghacks.net/2008/10/01/how-to-deal-with-huge-apache-web-server-log-files/#comment-494187</link>
		<dc:creator>pga</dc:creator>
		<pubDate>Wed, 01 Oct 2008 09:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=7325#comment-494187</guid>
		<description>just curious... how about using logrotate?</description>
		<content:encoded><![CDATA[<p>just curious&#8230; how about using logrotate?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
