<?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>FreeBSDologist.com</title>
	<atom:link href="http://freebsdologist.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://freebsdologist.com</link>
	<description>just testing WordPress 3</description>
	<lastBuildDate>Mon, 27 Jun 2011 08:19:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>lighttpd and WordPress</title>
		<link>http://freebsdologist.com/2011/06/lighttpd-and-wordpress/</link>
		<comments>http://freebsdologist.com/2011/06/lighttpd-and-wordpress/#comments</comments>
		<pubDate>Wed, 08 Jun 2011 16:45:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[not freebsd]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://freebsdologist.com/?p=15</guid>
		<description><![CDATA[By default, lighttpd will not support your WordPress installation and it won&#8217;t give you any information about why not. It&#8217;s a total pain but here&#8217;s how to get it up and running. lighttpd.conf Make sure &#8220;mod_fastcgi&#8221; is enabled in the server.modules section. Make sure you have the following lines: fastcgi.server = ( &#8220;.php&#8221; => (( [...]]]></description>
			<content:encoded><![CDATA[<p>By default, lighttpd will not support your WordPress installation and it won&#8217;t give you any information about why not. It&#8217;s a total pain but here&#8217;s how to get it up and running.</p>
<p><strong>lighttpd.conf</strong><br />
Make sure &#8220;mod_fastcgi&#8221; is enabled in the server.modules section.<br />
Make sure you have the following lines:</p>
<blockquote><p>fastcgi.server = ( &#8220;.php&#8221; => ((<br />
                     &#8220;bin-path&#8221; => &#8220;/usr/bin/php-cgi&#8221;,<br />
                     &#8220;socket&#8221; => &#8220;/tmp/php.socket&#8221;,<br />
                     &#8220;max-procs&#8221; => 2,<br />
                     &#8220;bin-environment&#8221; => (<br />
                       &#8220;PHP_FCGI_CHILDREN&#8221; => &#8220;16&#8243;,<br />
                       &#8220;PHP_FCGI_MAX_REQUESTS&#8221; => &#8220;10000&#8243;<br />
                     ),<br />
                     &#8220;bin-copy-environment&#8221; => (<br />
                       &#8220;PATH&#8221;, &#8220;SHELL&#8221;, &#8220;USER&#8221;<br />
                     ),<br />
                     &#8220;broken-scriptfilename&#8221; => &#8220;enable&#8221;<br />
                 )))
</p></blockquote>
<p>You may need to change some things around for your environment. Restart lighttpd and make sure it&#8217;s still working.<br />
Try reloading your WordPress site, for example and you&#8217;ll likely see <em>Your PHP installation appears to be missing the MySQL extension which is required by WordPress.</em><br />
You can solve this one of a number of ways. I just ran <em>sudo apt-get install php5-mysql</em>.<br />
Restart lighttpd.<br />
Assuming you have the correct database credentials, you should now be good to go. <img src='http://freebsdologist.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> .</p>
]]></content:encoded>
			<wfw:commentRss>http://freebsdologist.com/2011/06/lighttpd-and-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MyISAM table corruption causes</title>
		<link>http://freebsdologist.com/2010/10/myisam-table-corruption-causes/</link>
		<comments>http://freebsdologist.com/2010/10/myisam-table-corruption-causes/#comments</comments>
		<pubDate>Sun, 31 Oct 2010 11:09:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://freebsdologist.com/?p=12</guid>
		<description><![CDATA[Even though the MyISAM table format is very reliable (all changes to a table made by an SQL statement are written before the statement returns), you can still get corrupted tables if any of the following events occur: * The mysqld process is killed in the middle of a write. * An unexpected computer shutdown [...]]]></description>
			<content:encoded><![CDATA[<p> Even though the MyISAM table format is very reliable (all changes to a table made by an SQL statement are written before the statement returns), you can still get corrupted tables if any of the following events occur:</p>
<p>    * The mysqld process is killed in the middle of a write.<br />
    * An unexpected computer shutdown occurs (for example, the computer is turned off).<br />
    * Hardware failures.<br />
    * You are using an external program (such as myisamchk) to modify a table that is being modified by the server at the same time.<br />
    * A software bug in the MySQL or MyISAM code.</p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/corrupted-myisam-tables.html">MySQL has some additional documentation on this topic</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://freebsdologist.com/2010/10/myisam-table-corruption-causes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Remembering OSI Layers</title>
		<link>http://freebsdologist.com/2010/06/remembering-osi-layers/</link>
		<comments>http://freebsdologist.com/2010/06/remembering-osi-layers/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 11:40:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[application]]></category>
		<category><![CDATA[data link]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[OSI]]></category>
		<category><![CDATA[OSI model]]></category>
		<category><![CDATA[physical]]></category>
		<category><![CDATA[presentation]]></category>
		<category><![CDATA[session]]></category>
		<category><![CDATA[transport]]></category>

		<guid isPermaLink="false">http://freebsdologist.com/?p=9</guid>
		<description><![CDATA[All people seem to need data processing Application Presentation Session Transport Network Data link Physical]]></description>
			<content:encoded><![CDATA[<p><strong>A</strong>ll <strong>p</strong>eople <strong>s</strong>eem <strong>t</strong>o <strong>n</strong>eed <strong>d</strong>ata <strong>p</strong>rocessing</p>
<p>Application<br />
Presentation<br />
Session<br />
Transport<br />
Network<br />
Data link<br />
Physical</p>
]]></content:encoded>
			<wfw:commentRss>http://freebsdologist.com/2010/06/remembering-osi-layers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Forgotten MySQL Root Password</title>
		<link>http://freebsdologist.com/2010/06/forgotten-mysql-root-password/</link>
		<comments>http://freebsdologist.com/2010/06/forgotten-mysql-root-password/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 11:35:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[forgotten password]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[SQL]]></category>

		<guid isPermaLink="false">http://freebsdologist.com/?p=6</guid>
		<description><![CDATA[It happens to the best of us all the time. (Three times in a 24-hour period is my record&#8230;) On my Ubuntu VPSs, this is what I do when that happens: $-> /etc/init.d/mysql stop $-> mysqld_safe --skip-grant-tables &#038; $-> mysql -u root Use the &#8216;msyql&#8217; database to issue this query: UPDATE user set password=PASSWORD("ice_cream") where [...]]]></description>
			<content:encoded><![CDATA[<p>It happens to the best of us all the time. (Three times in a 24-hour period is my record&#8230;) On my Ubuntu VPSs, this is what I do when that happens:<br />
<code><br />
$-> /etc/init.d/mysql stop<br />
$-> mysqld_safe --skip-grant-tables &#038;<br />
$-> mysql -u root<br />
</code><br />
Use the &#8216;msyql&#8217; database to issue this query:<br />
<code>UPDATE user set password=PASSWORD("ice_cream") where User='root';</code><br />
Flush privs and then stop and start MySQL (normally).</p>
]]></content:encoded>
			<wfw:commentRss>http://freebsdologist.com/2010/06/forgotten-mysql-root-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is MySQL OK?</title>
		<link>http://freebsdologist.com/2010/06/is-mysql-ok/</link>
		<comments>http://freebsdologist.com/2010/06/is-mysql-ok/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 11:30:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[commands]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[mysqladmin]]></category>
		<category><![CDATA[ping]]></category>

		<guid isPermaLink="false">http://freebsdologist.com/?p=4</guid>
		<description><![CDATA[There are always many ways to skin a cat but here&#8217;s a neat way to check on MySQL: root@aleida:/home/aleida# mysqladmin -p ping Enter password: mysqld is alive Kinda neat, no?]]></description>
			<content:encoded><![CDATA[<p>There are always many ways to skin a cat but here&#8217;s a neat way to check on MySQL:</p>
<p><code>root@aleida:/home/aleida# mysqladmin -p ping<br />
Enter password:<br />
mysqld is alive</code></p>
<p>Kinda neat, no?</p>
]]></content:encoded>
			<wfw:commentRss>http://freebsdologist.com/2010/06/is-mysql-ok/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

