<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Apache, Linux ,Seo tricks and many more &#187; Apache</title>
	<atom:link href="http://www.gossiplime.com/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gossiplime.com</link>
	<description>This blog is just for all persons to know more about php, apache , linux , seo etc</description>
	<lastBuildDate>Wed, 08 Jul 2009 16:40:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>ls: command options</title>
		<link>http://www.gossiplime.com/2009/03/316/</link>
		<comments>http://www.gossiplime.com/2009/03/316/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 01:02:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=316</guid>
		<description><![CDATA[ls: command options Option Action -a                  list hidden files -d                  list the name of the current directory -F                  show directories with a trailing &#8216;/&#8217; executable files with a trailing &#8216;*&#8217; -g                  show group ownership of file in long listing -i                  print the inode number of [...]]]></description>
			<content:encoded><![CDATA[<p><strong>ls: command options</strong></p>
<p><strong>Option</strong> <strong>Action</strong></p>
<p>-a                  list hidden files</p>
<p>-d                  list the name of the current directory</p>
<p>-F                  show directories with a trailing &#8216;/&#8217;<br />
executable files with a trailing &#8216;*&#8217;</p>
<p>-g                  show group ownership of file in long listing</p>
<p>-i                  print the inode number of each file</p>
<p>-l                  long listing giving details about files<br />
and directories</p>
<p>-R                  list all subdirectories encountered</p>
<p>-t                  sort by time modified instead of name</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/03/316/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Install mod_bandwidth</title>
		<link>http://www.gossiplime.com/2009/03/install-mod_bandwidth/</link>
		<comments>http://www.gossiplime.com/2009/03/install-mod_bandwidth/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 16:46:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Videos]]></category>
		<category><![CDATA[mod_bandwidth]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=308</guid>
		<description><![CDATA[What is Mod_Bandwidth &#8220;Mod_bandwidth&#8221; (mod bandwidth) is a module for the Apache webserver that enable the setting of server-wide or per connection bandwidth limits, based on the directory, size of files and remote IP/domain. For Apache 1.3x. ONLY! This how-to is not compatible with old versions of apache, including but not limited to 1.3beta How [...]]]></description>
			<content:encoded><![CDATA[<p><strong>What is Mod_Bandwidth</strong></p>
<p>&#8220;Mod_bandwidth&#8221; (mod bandwidth) is a module for the Apache webserver that enable the setting of server-wide or per connection bandwidth limits, based on the directory, size of files and remote IP/domain.</p>
<p>For Apache 1.3x. ONLY! This how-to is not compatible with old versions of apache, including but not limited to 1.3beta</p>
<p><span style="color: #333399;"><strong>How to install mod_bandwidth</strong></span></p>
<p>1. Login to your server via SSH as root.</p>
<p>2. Type: mkdir /root/mod_bw</p>
<p>3. Type: cd /root/mod_bw</p>
<p>4. Type: wget ftp://ftp.cohprog.com/pub/apache/module/1.3.0/mod_bandwidth.c</p>
<p>5. Type: /usr/local/apache/bin/apxs -c /root/mod_bw/mod_bandwidth.c -o /usr/local/apache/libexec/mod_bandwidth.so</p>
<p>6. Type: mkdir /usr/local/apache/bw_limit</p>
<p>7. Type: mkdir /usr/local/apache/bw_limit/link</p>
<p>8. Type: mkdir /usr/local/apache/bw_limit/master</p>
<p>9. Type: pico -w /etc/httpd/conf/httpd.conf</p>
<p>10. Locate the following Line: LoadModule rewrite_module libexec/mod_rewrite.so</p>
<p>11. <strong>Before</strong> the above line add this:<br />
LoadModule bandwidth_module libexec/mod_bandwidth.so</p>
<p>12. Now locate this line: AddModule mod_env.c</p>
<p>13. <strong>Before</strong> the above line add this:<br />
AddModule mod_bandwidth.c</p>
<p>14. Now locate this line: # Document types.</p>
<p>15. <strong>Before</strong> the above line add this:<br />
BandWidthDataDir &#8220;/usr/local/apache/bw_limit&#8221;<br />
BandWidthModule On</p>
<p>16. To enable mod_bandwidth on a virtual host locate the virtual host entry for the specified domain/acount you wish to limit. Just before the line add the following:<br />
BandWidthModule On<br />
BandWidth all 512</p>
<p>The 512 can be replaced with whatever rate you wish to limit the acount too.</p>
<p>17. Save the file and exit.<br />
CTRL-X then Y then enter.</p>
<p>18. Type: service httpd restart</p>
<p>19. Type: cd /usr/sbin</p>
<p>20. Type: wget ftp://ftp.cohprog.com/pub/apache/module/cleanlink.pl</p>
<p><strong>What is cleanlink?</strong><br />
Cleanlink is a deamon that is used to clean links created by mod_bandwidth when they aren&#8217;t removed properly by the server. (When a httpd process doesn&#8217;t terminate the usual way.)</p>
<p>21. Type: chmod 755 cleanlink.pl</p>
<p>22. Type: pico -w cleanlink.pl</p>
<p>23. Change $LINKDIR to the following:<br />
$LINKDIR=&#8221;/usr/local/apache/bw_limit/link&#8221;;</p>
<p>24. Save the file and exit.<br />
CTRL-X then Y then enter.</p>
<p>25. Type: perl cleanlink.pl</p>
<p>26. Type: pico -w /etc/rc.d/rc.local</p>
<p>27. Scroll down to the very end of the file and add the following:<br />
# The following line Launches CleanLink for Mod_Bandwidth<br />
perl /usr/sbin/cleanlink.pl</p>
<p>28. Save the file and exit.<br />
CTRL-X then Y then enter.</p>
<p>mod_bandwidth has many options. If you wish to modify mod_bandwidth and enable more options please visit the documentation available by the programmer here: http://www.cohprog.com/v3/bandwidth/doc-en.html</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/03/install-mod_bandwidth/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Exim Failed &#8211; Exim is not running</title>
		<link>http://www.gossiplime.com/2009/02/exim-failed-exim-is-not-running/</link>
		<comments>http://www.gossiplime.com/2009/02/exim-failed-exim-is-not-running/#comments</comments>
		<pubDate>Fri, 27 Feb 2009 08:00:34 +0000</pubDate>
		<dc:creator>sps</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[cpanel]]></category>
		<category><![CDATA[exim]]></category>
		<category><![CDATA[mail]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=277</guid>
		<description><![CDATA[A restart was attempted automagically. Service Check Method: [check command] Cmd Service Check Raw Output: Exim is not running This is a bug in Exim here are the steps how i fix this problem Hello friends you can doit by SSH I first ran: /scripts/eximup &#8211;force &#8211;source I then removed the old exim RPM, which [...]]]></description>
			<content:encoded><![CDATA[<p>A restart was attempted automagically.<br />
Service Check Method:  [check command]</p>
<p>Cmd Service Check Raw Output: Exim is not running</p>
<p>This is a bug in Exim<br />
here are the steps how i fix this problem</p>
<p> Hello friends<br />
you can doit by SSH<br />
 I first ran:</p>
<p> /scripts/eximup &#8211;force &#8211;source</p>
<p> I then removed the old exim RPM, which was preventing the correct one from</p>
<p> being updated.</p>
<p> I then ran:</p>
<p> /scripts/eximup &#8211;force</p>
<p> Exim is now up well.</p>
<p> Thank you. <img src='http://www.gossiplime.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/02/exim-failed-exim-is-not-running/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Get Email when someone Login by root</title>
		<link>http://www.gossiplime.com/2009/02/get-email-when-someone-login-by-root/</link>
		<comments>http://www.gossiplime.com/2009/02/get-email-when-someone-login-by-root/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 09:06:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=256</guid>
		<description><![CDATA[Hi friends everybuddy wanted security about their webserver and updated everytime you can get an email when anybuddy login via root though ssh. To accomplish this you will need to edit the file .bash_profile. At command prompt type the below command: pico .bash_profile At the end of the file add following code: echo &#8216;ALERT &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p>Hi friends everybuddy wanted security about their webserver and updated everytime<br />
you can get an email when anybuddy login via root though ssh.</p>
<p>To accomplish this you will need to edit the file .bash_profile.<br />
At command prompt type the below command:</p>
<blockquote><p>pico .bash_profile</p></blockquote>
<p>At the end of the file add following code:</p>
<blockquote><p>echo &#8216;ALERT &#8211; Root Access from:&#8217; `date` `who` | mail -s &#8220;Alert: Root Access from `who | awk &#8216;{print $6}&#8217;`&#8221; admin@gmail.com</p></blockquote>
<p>Replace this with your email &#8220;admin@gmail.com&#8221;</p>
<p>If  anybuddy login via ssh root  then you will recieve an email.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/02/get-email-when-someone-login-by-root/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Install mod_limitipconn For Apache</title>
		<link>http://www.gossiplime.com/2009/02/install-mod_limitipconn-for-apache/</link>
		<comments>http://www.gossiplime.com/2009/02/install-mod_limitipconn-for-apache/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 17:59:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[connection]]></category>
		<category><![CDATA[mod]]></category>
		<category><![CDATA[mp3 limit]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=233</guid>
		<description><![CDATA[Installing mod_limitipconn.c This is the distribution page for the Apache module mod_limitipconn.c, which allows web server administrators to limit the number of simultaneous downloads permitted from a single IP address. Why did I write this module? Well, I run an mp3 server which since its inception was being constantly hosed by people who were trying [...]]]></description>
			<content:encoded><![CDATA[<p>Installing mod_limitipconn.c <img src='http://www.gossiplime.com/wp-includes/images/smilies/icon_surprised.gif' alt=':o' class='wp-smiley' /> </p>
<p>This is the distribution page for the Apache module mod_limitipconn.c, which<br />
allows web server administrators to limit the number of simultaneous<br />
downloads permitted from a single IP address.</p>
<p>Why did I write this module? Well, I run an mp3 server which since its<br />
inception was being constantly hosed by people who were trying to download<br />
dozens of files at once. For months I scoured the Internet looking for a<br />
code snippet that would solve this problem. The closest thing I found was this<br />
patch against an old version of Apache, and it didn&#8217;t run properly on my Linux box<br />
(that was back then; nowadays, the patch doesn&#8217;t even apply cleanly to the<br />
Apache source tree).</p>
<p>Finally I gave up and decided to write something to do the job myself, and<br />
here&#8217;s the result.<br />
=================<br />
Log into ssh</p>
<p>(Apache 1.3.x) -<br />
cd /usr/src<br />
<a title="mod limitpcorn" href="http://dominia.org/djao/limit/mod_limitipconn-0.04.tar.gz" target="_self">http://dominia.org/djao/limit/mod_limitipconn-0.04.tar.gz</a><br />
tar xzvf mod_limitipconn-0.04.tar.gz<br />
cd mod_limitipconn-0.04</p>
<p>(Apache 2.0.x)<br />
cd /usr/src<br />
<a title="mod limitpcorn" href="http://dominia.org/djao/limit/mod_limitipconn-0.22.tar.gz" target="_self">http://dominia.org/djao/limit/mod_limitipconn-0.22.tar.gz</a><br />
tar xzvf mod_limitipconn-0.22.tar.gz<br />
cd mod_limitipconn-0.22</p>
<p>pico Makefile<br />
find the line that reads APXS=apxs<br />
change that to<br />
APXS=/usr/local/apache/bin/apxs</p>
<p>press cntrl O to save<br />
then cntrl X</p>
<p>// if your locations to apxs is different<br />
locate apxs and copy the path<br />
then paste that in<br />
//</p>
<p>make<br />
make install</p>
<p>service httpd restart</p>
<p>pico -w /etc/httpd/conf/httpd.conf</p>
<p>locate ExtendedStatus<br />
Make sure ExtendedStatus is on and without the comment at the start</p>
<p>and add this line to every virtual directory you want to limit<br />
or add it once to the main directory to limit all</p>
<p>MaxConnPerIP 3<br />
# exempting images from the connection limit is often a good<br />
# idea if your web page has lots of inline images, since these<br />
# pages often generate a flurry of concurrent image requests<br />
NoIPLimit image/*</p>
<p>MaxConnPerIP 1<br />
# In this case, all MIME types other than audio/mpeg and video*<br />
# are exempt from the limit check<br />
OnlyIPLimit audio/mpeg video</p>
<p>press cntrl O to save<br />
then cntrl X<br />
then service</p>
<p>httpd restart<br />
 <img src='http://www.gossiplime.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' />  When i try it i have limit /download location and works really good. so dude enjoy <img src='http://www.gossiplime.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/02/install-mod_limitipconn-for-apache/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>All about httpd.conf</title>
		<link>http://www.gossiplime.com/2009/01/all-about-httpdconf/</link>
		<comments>http://www.gossiplime.com/2009/01/all-about-httpdconf/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 22:21:08 +0000</pubDate>
		<dc:creator>vinod</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[hostname]]></category>
		<category><![CDATA[httpd]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=163</guid>
		<description><![CDATA[This  httpd.conf file to set itself up for this particular configuration setup with: ServerType standalone The option ServerType specifies how Apache should run on the system. You can run it from the super-server inetd, or as standalone daemon. It&#8217;s highly recommended to run Apache in standalone type for better performance and speed. ServerRoot &#8220;/etc/httpd&#8221; The [...]]]></description>
			<content:encoded><![CDATA[<div class="glosslist">This  <tt class="filename">httpd.conf</tt> file to set itself up for this particular configuration setup with:</div>
<div class="glosslist">
<dl>
<dt><span style="color: #008080;"><strong><span class="envar">ServerType standalone</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">ServerType</tt> specifies how Apache should run on the system. You can run it from the super-server inetd, or as standalone daemon. It&#8217;s highly recommended to run Apache in standalone type for better performance and speed.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">ServerRoot &#8220;/etc/httpd&#8221;</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">ServerRoot</tt> specifies the directory in which the configuration files of the Apache server lives. It allows Apache to know where it can find its configuration files when it starts.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">PidFile</span> <span class="filename">/var/run/httpd.pid</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">PidFile</tt> specifies the location where the server will record the process id of the daemon when it starts. This option is only required when you configure Apache in standalone mode.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">ResourceConfig</span> <span class="filename">/dev/null</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">ResourceConfig</tt> specifies the location of the old <tt class="filename">srm.conf</tt> file that Apache read after it finished reading the <tt class="filename">httpd.conf</tt> file. When you set the location          to <tt class="filename">/dev/null,</tt> Apache allows you to include the content of this file in <tt class="filename">httpd.conf</tt> file, and in this manner, you have just one file that handles all your configuration          parameters for simplicity.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">AccessConfig</span> <span class="filename">/dev/null</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">AccessConfig</tt> specifies the location of the old <tt class="filename">access.conf</tt> file that Apache read after it finished reading the <tt class="filename">srm.conf</tt> file. When you set the location to <tt class="filename">/dev/null</tt>,         Apache allows you to include the content of this file in <tt class="filename">httpd.conf</tt> file, and in this manner, you have just one file that handles all your configuration parameters for simplicity.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">Timeout 300</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">Timeout</tt> specifies the amount of time Apache will wait for a GET, POST, PUT request and ACKs on transmissions. You can safely leave this option on its default values.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">KeepAlive On</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">KeepAlive</tt>, if set to <tt class="envar">On</tt>, specifies enabling persistent connections on this web server. For better performance, it&#8217;s recommended to set this option to <tt class="envar">On</tt>, and allow more than one request per connection.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">MaxKeepAliveRequests 0</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">MaxKeepAliveRequests</tt> specifies the number of requests allowed per connection when the <tt class="envar">KeepAlive</tt> option above is set to <tt class="envar">On.</tt> When the value of this option is set to <tt class="envar">0</tt> then unlimited          requests are allowed on the server. For server performance, it&#8217;s recommended to allow unlimited requests.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">KeepAliveTimeout 15</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">KeepAliveTimeout</tt> specifies how much time, in seconds, Apache will wait for a subsequent request before closing the connection. The value of <tt class="envar">15</tt> seconds is a good average for server performance.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">MinSpareServers 16</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">MinSpareServers</tt> specifies the minimum number of idle child server processes for Apache, which is not handling a request. This is an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of <tt class="envar">16</tt> is recommended by various benchmarks on the Internet.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">MaxSpareServers 64</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">MaxSpareServers</tt> specifies the maximum number of idle child server processes for Apache, which is not handling a request. This is also an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of <tt class="envar">64</tt> is recommended by various benchmarks on the Internet.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">StartServers 16</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">StartServers</tt> specifies the number of child server processes that will be created by Apache on start-up. This is, again, an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of <tt class="envar">16</tt> is recommended by various benchmarks on the Internet.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">MaxClients 512</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">MaxClients</tt> specifies the number of simultaneous requests that can be supported by Apache. This too is an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of <tt class="envar">512</tt> is recommended by various benchmarks on the Internet.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">MaxRequestsPerChild 100000</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">MaxRequestsPerChild</tt> specifies the number of requests that an individual child server process will handle. This too is an important tuning parameter regarding the performance of the Apache web server.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">User www</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">User</tt> specifies the <span class="acronym">UID</span> that Apache server will run as. It&#8217;s important to create a new user that has minimal access to the system, and functions just for the purpose of running the web server daemon.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">Group www</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">Group</tt> specifies the <span class="acronym">GID</span> the Apache server will run as. It&#8217;s important to create a new group that has minimal access to the system and functions just for the purpose of running the web server daemon.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">DirectoryIndex index.htm index.html index.php index.php3 default.html index.cgi</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">DirectoryIndex</tt> specifies the files to use by Apache as a pre-written <span class="acronym">HTML</span> directory index. In other words, if Apache can&#8217;t find the default index page to display, it&#8217;ll try the next entry in this parameter, if available. To improve performance of your web server it&#8217;s recommended to list the most used default index pages of your web site first.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">Include conf/mmap.conf</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">Include</tt> specifies the location of other files that you can include from within the server configuration files <tt class="filename">httpd.conf</tt>. In our case, we include the <tt class="filename">mmap.conf</tt> file located          under <tt class="filename">/etc/httpd/conf</tt> directory. This file <tt class="filename">mmap.conf</tt> maps files into memory for faster serving.</p></blockquote>
</dd>
<dt><span style="color: #008080;"><strong><span class="envar">HostnameLookups Off</span></strong></span></dt>
<dd>
<blockquote><p>The option <tt class="envar">HostnameLookups</tt>, if set to <tt class="envar">Off</tt>, specifies the disabling of <span class="acronym">DNS</span> lookups. It&#8217;s recommended to set this option to <tt class="envar">Off</tt> in order to save the network traffic time, and to improve          the performance of your Apache web server.</p></blockquote>
</dd>
</dl>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2009/01/all-about-httpdconf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Zone transfer AXFR + Change or Disable Name Server version</title>
		<link>http://www.gossiplime.com/2008/09/zone-transfer-axfr/</link>
		<comments>http://www.gossiplime.com/2008/09/zone-transfer-axfr/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 10:07:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[AXFR]]></category>
		<category><![CDATA[Linux.Apace]]></category>
		<category><![CDATA[named.conf]]></category>
		<category><![CDATA[NS]]></category>

		<guid isPermaLink="false">http://www.gossiplime.com/?p=160</guid>
		<description><![CDATA[At least one of your nameservers allowed a zone transfer to be performed. The zone transfer enables the extraction of all DNS data available for the zone. According to DNS best practices it is advisable to disable zone transfers for public slave zones. To disable zone transfer Login with root edit named.conf root@server [~]# vi [...]]]></description>
			<content:encoded><![CDATA[<p>At least one of your nameservers allowed a zone transfer to be performed.  The zone transfer enables the extraction of all DNS data available for the zone.  According to DNS best practices it is advisable to disable zone transfers for public slave zones.</p>
<p>To disable zone transfer</p>
<p>Login with root</p>
<p>edit named.conf</p>
<p>root@server [~]# vi /etc/named.conf</p>
<p>by setting this in options {}</p>
<p>allow-transfer { }; 		<!-- / message --> <!-- controls --></p>
<p>root@server [~]# :wq</p>
<p><img class="alignnone size-full wp-image-174" title="axfr-ns" src="http://www.gossiplime.com/wp-content/uploads/2008/09/axfr-ns.jpg" alt="axfr-ns" width="510" height="513" /></p>
<p>Those persons who want to <strong>change there or disable thier nameserver Version</strong> do as writen in the above image.</p>
<p>version  &#8221; &#8221; ;</p>
<p>This will disable your name server Version</p>
<p>That&#8217;s it you are done..</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gossiplime.com/2008/09/zone-transfer-axfr/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

