<?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>Albertech.net &#187; Linux</title>
	<atom:link href="http://albertech.net/category/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://albertech.net</link>
	<description>Guides and Reviews for WordPress, PHP, MySQL, Apache, CMS Systems, jQuery, and other Technologies</description>
	<lastBuildDate>Tue, 31 Jan 2012 17:31:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Installing nginx with PHP, MySQL, and WordPress in Fedora</title>
		<link>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/</link>
		<comments>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/#comments</comments>
		<pubDate>Fri, 01 Apr 2011 17:31:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[Fedora install]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=663</guid>
		<description><![CDATA[Interested in installing nginx on a Fedora system? The configuration with nginx is more complicated than Apache since  it requires the setup of the nginx server and a separate daemon for running PHP. I prefer creating the daemon from scratch rather than going with the fpm route in Fedora 14 since there isn't official support for it. I'd certainly install the fpm package once its available in Fedora.

<strong>Why switch to nginx? </strong>

If you have a site with heavy CPU and memory load in Apache, then nginx is a great choice. I recently made the switch to nginx and have noticed a reduction in CPU and memory usage. Nginx loads static content very fast and efficiently.

Here's a graph of my nginx server load test. Courtesy of <a href="http://loadimpact.com/" target="_blank">LoadImpact</a>'s free load testing service.

<img class="alignnone size-full wp-image-666" title="nginx-blogs" src="http://albertech.net/wp-content/uploads/2011/04/nginx-blogs.png" alt="" width="544" height="335" />

The user load time on my server is minimally impacted with 50 clients viewing the site simultaneously.]]></description>
		<wfw:commentRss>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIX: Fedora SELinux permissions for PHP file upload</title>
		<link>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/</link>
		<comments>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/#comments</comments>
		<pubDate>Wed, 02 Mar 2011 23:27:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[SELinux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=643</guid>
		<description><![CDATA[By default, SELinux will block the ability for Apache/webapps to write to files in Fedora. This is a security feature to limit what folders Apache can write to. You can notice this issue if you get errors in your Apache logs such as:

PHP Warning:  move_uploaded_file(): Unable to move '/tmp/...' to '.......'

<strong>Command to set permissions:</strong>

<code>chcon -R -t httpd_sys_rw_content_t [Name of Folder]</code>

You can check the SELinux permissions via the following command:
<code>ls -halZ</code>]]></description>
		<wfw:commentRss>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Issues with Debian Lenny and Tomcat 5.5</title>
		<link>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/</link>
		<comments>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 01:00:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Tomcat]]></category>
		<category><![CDATA[tomcat 5.5]]></category>
		<category><![CDATA[tomcat 6]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=520</guid>
		<description><![CDATA[<strong>Is your Debian install of Tomcat 5.5 not working with your Webapp?</strong>

Just a heads up for anyone with problems trying to get webapps working with Debian. I highly recommend installing Tomcat 6.0 from source. It helped clear a number of issues for me. Debian only supports Tomcat 5.5 in their package management system. I could have gone with unstable to get Tomcat 6.0, but I prefer not to deal with their folder organization layout (see below)

<strong>Here are a few resources I've used to install Tomcat 6.0 in Debian Lenny. </strong>

<ol><li>
<a href="http://www.ctrip.ufl.edu/tomcat6-debian-lenny-howto" target="_blank"><strong>How to Install Tomcat 6 in Debian Lenny</strong></a>. This is an <strong>excellent</strong> step-by-step tutorial. A+ in my book.
<li>
<a href="http://www.mysql.com/downloads/connector/j/" target="_blank"><strong>http://www.mysql.com/downloads/connector/j/</strong></a>  Connector/J, MySQL JDBC Connector download.
<li>
<a href="http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html" target="_blank"><strong>http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html</strong></a>. Tomcat 6.0 configuration with MySQL Connector/J JDBC.
</ol>

]]></description>
		<wfw:commentRss>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fix: Webmin error &#8220;This Webmin module depends on the module phpini&#8221;</title>
		<link>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/</link>
		<comments>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 17:49:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[webmin]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=514</guid>
		<description><![CDATA[Upon updating Webmin, I noticed that there is a new package dependency that breaks the updates.

To fix, you will need to get the phpini package from Webmin <a href="http://www.webmin.com/standard.html">http://www.webmin.com/standard.html</a> and extract the folder to your Webmin system folder. In Debian, its located in /usr/share/webmin/   This should also apply to any other Webmin packages that are missing from your system.]]></description>
		<wfw:commentRss>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix: installing scponly on Debian 5.0</title>
		<link>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/</link>
		<comments>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/#comments</comments>
		<pubDate>Wed, 06 Oct 2010 00:37:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=470</guid>
		<description><![CDATA[Scponly is used for chroot to limit server access for SSH and SFTP users. Unfortunately, the Debian package for scponly does not work with Debian 5.0.

If you upgraded from Debian 4 to Debian 5 and are using scponly, you may notice that the clients are unable to connect. Possible error messages include:
<ul>
	<li>"failed WinSCP compatibility mode" error message</li>
	<li>WinSCP closes unexpectedly after authenticating</li>
	<li>Connection failure after successful authentication</li>
	<li>Client logs two attempts to connect to the /home/username home directory before failing
<span id="more-470"></span></li>
</ul>
<strong>The fix is to remove scponly package in Debian and install a newer version from source code. Download the scponly source at:
</strong>

<a href="http://sublimation.org/scponly/wiki/index.php/Main_Page" ... ]]></description>
		<wfw:commentRss>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable autostart of MySQL in Debian and Ubuntu</title>
		<link>http://albertech.net/2010/07/disable-autostart-of-mysql-in-debian-and-ubuntu/</link>
		<comments>http://albertech.net/2010/07/disable-autostart-of-mysql-in-debian-and-ubuntu/#comments</comments>
		<pubDate>Wed, 07 Jul 2010 17:39:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL debian autostart]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=427</guid>
		<description><![CDATA[The quickest way to disable autostart of services in Debian is to utilize a convenient curses interface to selectively choose which services to autostart in different run levels. Its so much easier to use than update-rc.d.  Its good for instances where you are migrating services out of an existing box, such as removing the mysql server without uninstalling.

The package is called:
<strong>sysv-rc-conf</strong>

(Install it using aptitude or apt-get install)]]></description>
		<wfw:commentRss>http://albertech.net/2010/07/disable-autostart-of-mysql-in-debian-and-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amanda Backup: Client installation on Debian</title>
		<link>http://albertech.net/2010/01/amanda-backup-client-installation-on-debian/</link>
		<comments>http://albertech.net/2010/01/amanda-backup-client-installation-on-debian/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 20:28:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[amanda]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[install]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=356</guid>
		<description><![CDATA[If you install the amanda-client package on Debian, some things need to be configured before you can actually use the service. By default, the server will not be able to connect to the client. The common error is: "selfcheck request failed: timeout waiting for ACK". Read the post for the solution.]]></description>
		<wfw:commentRss>http://albertech.net/2010/01/amanda-backup-client-installation-on-debian/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SFTP/ScpOnly: Fix for WinSCP Error</title>
		<link>http://albertech.net/2009/11/sftp-scponly-fix-for-winscp-error/</link>
		<comments>http://albertech.net/2009/11/sftp-scponly-fix-for-winscp-error/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 22:26:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[ScpOnly]]></category>
		<category><![CDATA[SFTP]]></category>
		<category><![CDATA[WinSCP]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=321</guid>
		<description><![CDATA[Here's the fix for the common error with ScpOnly when using the Jail SFTP option. The error message for WinSCP clients is "WinSCP: this is end-of-file:0 failed with invalid output" when trying to connect to a SFTP server. View the post to see the fix for WinSCP.]]></description>
		<wfw:commentRss>http://albertech.net/2009/11/sftp-scponly-fix-for-winscp-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: Installing Mailman with Exim4</title>
		<link>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/</link>
		<comments>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 21:03:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=283</guid>
		<description><![CDATA[I recently installed Mailman with Exim4, which was a challenge considering all the manual configuration you have to do. I found a few guides on the install, but they didn't seem to be "complete" enough to get the system working. Turns out, the biggest challenge was Exim4. The configuration files are confusing, especially since there are two sets of configuration files. ]]></description>
		<wfw:commentRss>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>awstats: Import old log files</title>
		<link>http://albertech.net/2009/09/awstats-import-old-log-files/</link>
		<comments>http://albertech.net/2009/09/awstats-import-old-log-files/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 16:26:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[awstats]]></category>
		<category><![CDATA[import]]></category>
		<category><![CDATA[old logs]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=256</guid>
		<description><![CDATA[One thing I've encountered with Awstats is adding in old apache log files. This is useful if you are migrating data from servers. By default, Awstats will ignore ALL past dates in the log that occur before the most recent log entry date. In order to avoid Awstats from finding the "recent log entry date", you will need move all Awstats cached files into a separate folder. ]]></description>
		<wfw:commentRss>http://albertech.net/2009/09/awstats-import-old-log-files/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WordPress MU: Limit access to certain blogs</title>
		<link>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/</link>
		<comments>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 20:22:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[limit access]]></category>
		<category><![CDATA[wordpress mu]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=203</guid>
		<description><![CDATA[I recently implemented a way to limit access by IP range on specific blogs on WordPress MU. As you know, WordPress MU uses Apache Rewrite engine to rewrite URLs. For instance, you have a blog on WordPress MU called "intranet". Apache Rewrite takes the "intranet" string in the URL and automatically rewrites it as a value in the PHP script. A side effect to Apache Rewrite is that "Directory" .htaccess parameters don't work. So, if you wanted only your company IPs to access an internal blog, you will need to use Apache Rewrite parameters instead. For the solution, read on...]]></description>
		<wfw:commentRss>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: Fix for Mailman server that won&#8217;t start</title>
		<link>http://albertech.net/2009/07/debian-fix-for-mailman-server-that-wont-start/</link>
		<comments>http://albertech.net/2009/07/debian-fix-for-mailman-server-that-wont-start/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 19:49:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[mailman]]></category>
		<category><![CDATA[qrunner]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=200</guid>
		<description><![CDATA[Recently, there was a Mailman upgrade that seems to break Mailman if you don't have a list called "mailman" on your server. Symptoms of this error include:

/var/log/mailman/error
<code>mailmanctl(2801): PID unreadable in: /var/run/mailman/mailman.pid
mailmanctl(2801): [Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
mailmanctl(2801): Is qrunner even running?
</code>

If you try to restart mailman
<code>/etc/rc2.d/S20mailman restart</code>
and get the same error, then you need to check whether you have a "mailman" list on your server.

To install mailman list, follow this resource:
<a href="http://www.askdavetaylor.com/why_is_mailman_complaining_site_list_is_missing_mailman.html">http://www.askdavetaylor.com/why_is_mailman_complaining_site_list_is_missing_mailman.html</a>

After installing the mailman list, you can try restarting the mailman qrunner service to see if it works.
<code>/etc/rc2.d/S20mailman start</code>]]></description>
		<wfw:commentRss>http://albertech.net/2009/07/debian-fix-for-mailman-server-that-wont-start/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: fixing GPG error on apt-get update</title>
		<link>http://albertech.net/2009/06/debian-fixing-gpg-error-on-apt-get-update/</link>
		<comments>http://albertech.net/2009/06/debian-fixing-gpg-error-on-apt-get-update/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 22:14:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[gpg error]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=179</guid>
		<description><![CDATA[<strong>If you get a GPG error when doing an apt-get update</strong>, here's the quickest way to fix it.The error message looks similar to:
<blockquote>W: GPG error: http://security.debian.org etch/updates Release:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY XXXXXXXXXXX: There is no public key available for the following key IDs: W: You may want to run apt-get update to correct these problems</blockquote>
By default, it says "You may want to run apt-get update to correct these problems". The problem is, apt-get update doesn't fix the keys automagically. To fix, you will need to update the debian keyring by ... ]]></description>
		<wfw:commentRss>http://albertech.net/2009/06/debian-fixing-gpg-error-on-apt-get-update/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Debian on VMWARE: Installing VMWare Tools</title>
		<link>http://albertech.net/2009/05/debian-on-vmware-installing-vmware-tools/</link>
		<comments>http://albertech.net/2009/05/debian-on-vmware-installing-vmware-tools/#comments</comments>
		<pubDate>Fri, 15 May 2009 21:54:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMWARE]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[install vmware tools]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=164</guid>
		<description><![CDATA[<strong>Why install VMWARE Tools?
</strong>Improved display support with SVGA driver
Cut and paste from host onto the VMWare guest
Automation of guest operating system commands
Sync time
Shrinking disk space
Startup and shutdown scripts

<strong>In order to install VMWARE tools on Debian, you will need to make sure you have the package "linux-headers-[kernel version]" installed.</strong>

If not, you will get a prompt during the configuration asking for the path of the C header files.

To find the version of your kernel, type in:
<strong>uname -a</strong>

It should say something like Linux infomine 2.6.26-2-amd64 (with your current CPU architecture at the end)

****
NOTE: Do this at your own risk. If you put the ... ]]></description>
		<wfw:commentRss>http://albertech.net/2009/05/debian-on-vmware-installing-vmware-tools/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian on VMWARE: Troubleshoot Network</title>
		<link>http://albertech.net/2009/05/debian-on-vmware-troubleshoot-network/</link>
		<comments>http://albertech.net/2009/05/debian-on-vmware-troubleshoot-network/#comments</comments>
		<pubDate>Tue, 12 May 2009 00:50:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMWARE]]></category>
		<category><![CDATA[clone network]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=162</guid>
		<description><![CDATA[Ever change the Network MAC address setting in VMWARE and you can't get the network to work?

Here's a quick how-to on changing the MAC address on a Linux VM. This is useful if you want to clone an existing machine and want to have both machines running with network at the same time. I am using VMWARE Server 2.0. (free version)
]]></description>
		<wfw:commentRss>http://albertech.net/2009/05/debian-on-vmware-troubleshoot-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: Broken grub after Lenny upgrade</title>
		<link>http://albertech.net/2009/05/debian-broken-grub-after-lenny-upgrade/</link>
		<comments>http://albertech.net/2009/05/debian-broken-grub-after-lenny-upgrade/#comments</comments>
		<pubDate>Fri, 01 May 2009 10:49:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[lenny upgrade]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=156</guid>
		<description><![CDATA[I've done multiple Debain upgrades from Etch to Lenny and have noticed there are some issues with grub breaking. The upgrade somehow puts the wrong hard drive information in the default grub file. Here's some recommendations on how to perform the Lenny upgrade]]></description>
		<wfw:commentRss>http://albertech.net/2009/05/debian-broken-grub-after-lenny-upgrade/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Amanda Backups: Exclude.gtar</title>
		<link>http://albertech.net/2009/04/amanda-backups-excludegtar/</link>
		<comments>http://albertech.net/2009/04/amanda-backups-excludegtar/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 22:39:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[exclude.gtar]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=152</guid>
		<description><![CDATA[The Amanda backup system is a great resource for backing up your Linux system. One of the things I noticed with the latest version is that the exclusion list has been breaking. For instance, Amanda backups are now backing up the /tmp folder, which causes it complain with the PHP session lock files. All was needed to fix was adding a leading dot in front of each folder.]]></description>
		<wfw:commentRss>http://albertech.net/2009/04/amanda-backups-excludegtar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>KDE: How to fix &#8220;No greeter widget plugin loaded&#8221; error</title>
		<link>http://albertech.net/2009/04/kde-how-to-fix-no-greeter-widget-plugin-loaded-error/</link>
		<comments>http://albertech.net/2009/04/kde-how-to-fix-no-greeter-widget-plugin-loaded-error/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 21:38:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[greeter widget]]></category>
		<category><![CDATA[kde]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=142</guid>
		<description><![CDATA[I was helping one of the staff today with their Debian setup. KDE somehow broke after they did an apt-get update. Turns out there must have been like 40-50 packages that must have been in the update and thus one of them broke during the upgrade.

Upon startup, there was a unique error message that came up with KDE during the startup phase -- "No greeter widget plugin loaded. Check the configuration." with an OK box. Clicking the OK box would lead to KDE exiting to shell. Reinstalling kdm had no effect. The fix? Read the article to see...]]></description>
		<wfw:commentRss>http://albertech.net/2009/04/kde-how-to-fix-no-greeter-widget-plugin-loaded-error/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>Analyzing large web log files</title>
		<link>http://albertech.net/2009/02/parse-large-logfile/</link>
		<comments>http://albertech.net/2009/02/parse-large-logfile/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 05:11:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[log files]]></category>
		<category><![CDATA[regular expressions]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=91</guid>
		<description><![CDATA[<strong>The fastest way to trim down large web log files is through UNIX/Linux shell</strong>. Large files exceeding 1 GB (millions of lines of logs) are not easily editable using a GUI interface, so the fastest way is to parse them is via command line. You can trim them down according to a time range, remove internal requests from within the company, and remove bots/crawlers data from the log files.

For instance, I have a 4GB log file with about two years worth of info (2007-2009) in there. What if I just wanted the logs from 2008? First, run the "head -10" command ... ]]></description>
		<wfw:commentRss>http://albertech.net/2009/02/parse-large-logfile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Awstats setup in Debian</title>
		<link>http://albertech.net/2009/01/awstats-debiansetup/</link>
		<comments>http://albertech.net/2009/01/awstats-debiansetup/#comments</comments>
		<pubDate>Mon, 26 Jan 2009 03:05:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[awstats]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[geoIP]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=65</guid>
		<description><![CDATA[<strong>Installing awstats in Debian with GeoIP caching
</strong>

<strong>First, use apt-get to get the software:</strong>

apt-get install awstats

<strong>Configure awstats:</strong>
Instead of using the awstats configure tool (written in Perl), manually add in the awstats Apache configuration. Using the <a href="http://www.debuntu.org/2006/04/21/33-how-to-setting-up-awstats-with-apache-2-on-debianubuntu">tutorial from debuntu</a>, make a file inside your apache config folder called awstats.conf with the following lines.

<code>Alias /awstatsclasses "/usr/share/awstats/lib/"
Alias /awstats-icon/ "/usr/share/awstats/icon/"
Alias /awstatscss "/usr/share/doc/awstats/examples/css"
Options ExecCGI -MultiViews +SymLinksIfOwnerMatch</code>

<strong>Inside the Apache2.conf file (or virtual host conf file inside the sites-available folder) add this to the end of the file:</strong>

<code>Include /etc/apache2/awstats.conf</code>

<strong>Next, copy the /usr/lib/cgi-bin/awstats.pl file to the apache cgi-bin folder.</strong> If you have virtual hosts enabled, copy it to ... ]]></description>
		<wfw:commentRss>http://albertech.net/2009/01/awstats-debiansetup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

