<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://ndcservers.net/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel>
        <title>Wiki</title>
        <description></description>
        <link>http://ndcservers.net/wiki/</link>
        <lastBuildDate>Sat, 31 Jul 2010 17:54:43 -0700</lastBuildDate>
        <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
        <image>
            <url>http://ndcservers.net/wiki/lib/images/favicon.ico</url>
            <title>Wiki</title>
            <link>http://ndcservers.net/wiki/</link>
        </image>
        <item>
            <title>Unable to Edit Cronjobs through cPanel</title>
            <link>http://ndcservers.net/wiki/cpanel/unable-to-edit-cronjob?rev=1279313815&amp;do=diff</link>
            <description>Chances are the problem is that  has lost it's suid privileges. To correct this run the following command as root via SSH or the console:

casino en ligne

# chmod 4755 /usr/bin/crontab

cpanel,
	cron</description>
            <author>TierraTaplin</author>
        <category>cpanel</category>
        <category>cron</category>
            <pubDate>Fri, 16 Jul 2010 13:56:55 -0700</pubDate>
        </item>
        <item>
            <title>Hardening your TCP/IP Stack Against SYN Floods - created</title>
            <link>http://ndcservers.net/wiki/server-administration/hardening-tcpip-syn-flood?rev=1277763621&amp;do=diff</link>
            <description>Hardening your TCP/IP Stack Against SYN Floods


Denial of service (DoS) attacks launch via SYN floods can be very problematic for servers that are not properly configured to handle them. Proper firewall filtering policies are certainly usually the first line of defense, however the Linux kernel can also be hardened against these types of attacks. This type of hardening is useful for SYN floods that attempt to overload a particular service with requests (such as http) as opposed to one that inte…</description>
            <author>Garrett Plasky</author>
        <category>guide</category>
        <category>shell</category>
        <category>security</category>
            <pubDate>Mon, 28 Jun 2010 15:20:21 -0700</pubDate>
        </item>
        <item>
            <title>ImageMagick [Imagick] PHP Class Broken or Fails to Install - created</title>
            <link>http://ndcservers.net/wiki/server-administration/imagick-class-error?rev=1277250288&amp;do=diff</link>
            <description>ImageMagick [Imagick] PHP Class Broken or Fails to Install


Some versions of CentOS (including the most recent 5.5) have an issue with a buggy 6.4.8 RPM version of ImageMagick. This version prevents the Imagick PHP class from working properly, and also prevents the extension from being installed via PECL. If you are using the Imagick PHP class on your site, you will see an error something like:</description>
            <author>Garrett Plasky</author>
        <category>administration</category>
        <category>apache</category>
        <category>centos</category>
        <category>cpanel</category>
        <category>php</category>
            <pubDate>Tue, 22 Jun 2010 16:44:48 -0700</pubDate>
        </item>
        <item>
            <title>Compiling PHP on CentOS 5 (64bit) with MySQL Support - created</title>
            <link>http://ndcservers.net/wiki/apache/building-php-with-mysql-on-centos-5-64bit?rev=1277248219&amp;do=diff</link>
            <description>If you try to build PHP 5.x.x on a 64bit CentOS install you may get this error:

checking for specified location of the MySQL UNIX socket... no
checking for MySQL UNIX socket location... /var/lib/mysql/mysql.sock
checking for mysql_close in -lmysqlclient... no
checking for mysql_error in -lmysqlclient... no
configure: error: mysql configure failed. Please check config.log for more information.</description>
            <author>Garrett Plasky</author>
        <category>apache</category>
        <category>centos</category>
        <category>how-to</category>
        <category>mysql</category>
        <category>php</category>
            <pubDate>Tue, 22 Jun 2010 16:10:19 -0700</pubDate>
        </item>
        <item>
            <title>Redirect non-www Traffic to www Using mod_rewrite</title>
            <link>http://ndcservers.net/wiki/server-administration/redirect-non-www-to-www?rev=1277248012&amp;do=diff</link>
            <description>Moved to the Apache category.</description>
            <author>Garrett Plasky</author>
        <category>server-administration</category>
            <pubDate>Tue, 22 Jun 2010 16:06:52 -0700</pubDate>
        </item>
        <item>
            <title>Redirect non-www Traffic to www Using mod_rewrite - created</title>
            <link>http://ndcservers.net/wiki/apache/redirect-non-www-to-www?rev=1277247982&amp;do=diff</link>
            <description>This is an example using the mod_rewrite Apache module to force all traffic to your site to www.yourodmain.com. This can be useful in an SSL context, as well as for SEO purposes. Create a .htaccess file in your webroot (public_html for cPanel servers) and add the following lines:</description>
            <author>Garrett Plasky</author>
        <category>apache</category>
        <category>how-to</category>
            <pubDate>Tue, 22 Jun 2010 16:06:22 -0700</pubDate>
        </item>
    </channel>
</rss>
