<?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>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
	<atom:link href="http://thern.org/category/linux-and-freebsd/feed/" rel="self" type="application/rss+xml" />
	<link>http://thern.org</link>
	<description>Migrating servers to new datacenters or IP addresses is never entirely problem free, usually due to many DNS servers on the internet not obeying TTL's or caching old records for way too long.
These old cached DNS records (usually at different ISP's, major mailservers like google, hotmail, yahoo, etc.) cause problems where they'll route mail to your old server's IP even if you update your DNS.  This also results in clients connecting to your old web IP address and not hitting your new server.
When migrating static html sites, having two servers online during a migration isn't a real issue, but when you've got database driven websites (forums, blogs, etc.) this will result in updates going to two different sites, causing all sorts of hassles.  The way around this is to set up your old site as a proxy only, and proxy the results to the new IP address.
Here's some configs to allow for proxying Web traffic via Apache, DNS traffic via bind9, and Mail traffic via sen</description>
	<lastBuildDate>Sat, 03 Apr 2010 00:47:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/</link>
		<comments>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 00:45:34 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[sendmail]]></category>
		<category><![CDATA[system administration]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[dns proxy]]></category>
		<category><![CDATA[ip address]]></category>
		<category><![CDATA[ip migration]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mailertable]]></category>
		<category><![CDATA[mod_proxy]]></category>
		<category><![CDATA[named]]></category>
		<category><![CDATA[nameservers]]></category>
		<category><![CDATA[relay-domains]]></category>
		<category><![CDATA[ttl]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://thern.org/?p=201</guid>
		<description><![CDATA[Migrating servers to new datacenters or IP addresses is never entirely problem free, usually due to many DNS servers on the internet not obeying TTL's or caching old records for way too long. These old cached DNS records (usually at different ISP's, major mailservers like google, hotmail, yahoo, etc.) cause problems where they'll route mail [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/vmware-2-0-x-and-centos-5-4-glibc-crashes-and-instabilities-a-workaround-solution/</link>
		<comments>http://thern.org/linux-and-freebsd/vmware-2-0-x-and-centos-5-4-glibc-crashes-and-instabilities-a-workaround-solution/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 08:38:23 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[5.3]]></category>
		<category><![CDATA[5.4]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[glibc]]></category>
		<category><![CDATA[repos]]></category>
		<category><![CDATA[yum]]></category>

		<guid isPermaLink="false">http://thern.org/?p=191</guid>
		<description><![CDATA[If you're running VMWare Server 2.0.x on CentOS 5.4, you'll have noticed that you (most likely) suffer random reboots and other instabilities on the guest operating systems - this is due to a glibc error in vmware's libraries, and has yet to be fixed by vmware (thanks a lot).  The real issue is CentOS/Redhat has [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/vmware-2-0-x-and-centos-5-4-glibc-crashes-and-instabilities-a-workaround-solution/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/yum-update-check-script-runs-via-crontab-and-emails-when-new-updates-are-available/</link>
		<comments>http://thern.org/linux-and-freebsd/yum-update-check-script-runs-via-crontab-and-emails-when-new-updates-are-available/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 05:03:32 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[crontab]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[yum]]></category>
		<category><![CDATA[yum update]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=160</guid>
		<description><![CDATA[Here's a quick script that will check yum updates and email you when there are new updates available. Split into two sections, one script is for all package updates, and the other script is for letting us know if we need to reboot when a new kernel package has been installed. Script to check for [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/yum-update-check-script-runs-via-crontab-and-emails-when-new-updates-are-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/logrotate-tweaks-to-enhance-rsync-backups/</link>
		<comments>http://thern.org/linux-and-freebsd/logrotate-tweaks-to-enhance-rsync-backups/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 08:19:55 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[logrotate]]></category>
		<category><![CDATA[rsync]]></category>
		<category><![CDATA[time based logs]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=109</guid>
		<description><![CDATA[logrotate, by default (at least on CentOS as of 3, 4, and 5.x), rotates logs by incrementing all numbers on previous logs by one, and moving the current log to log.0 This is all fine and good if you like your logs to all be rotated in order, and have a certain number backed up: [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/logrotate-tweaks-to-enhance-rsync-backups/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/openvz-cache-update-script/</link>
		<comments>http://thern.org/linux-and-freebsd/openvz-cache-update-script/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 04:23:30 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[apt-get]]></category>
		<category><![CDATA[cache update]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[openvz]]></category>
		<category><![CDATA[templates]]></category>
		<category><![CDATA[yum]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=94</guid>
		<description><![CDATA[Script to update OpenVZ vz cache for any template. Useful to upgrade to newest security releases. #!/bin/bash # # updates cache of VZ # # # # Set These (or pass from command line as below) # #TEMPLATE=centos-5-i386-afull VZID=5999 # # use this from command line: # # ./updatevzcache centos-5-i386-afull # TEMPLATE=$1 # VZID=$2 # [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/openvz-cache-update-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/plesk-9-x-overuse-policy/</link>
		<comments>http://thern.org/linux-and-freebsd/plesk-9-x-overuse-policy/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 09:25:35 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[cli]]></category>
		<category><![CDATA[client_pref]]></category>
		<category><![CDATA[plesk]]></category>
		<category><![CDATA[suspend]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=82</guid>
		<description><![CDATA[Parallels, in their infinite wisdom, introduced new "overuse" policies into their Plesk control panel as of version 9.0.  A great idea when just starting out, but a nightmare when upgrading from a previous version, since it changes the default behavior when clients and domain owners reach their pre-assigned limits.  Now, instead of just warning that [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/plesk-9-x-overuse-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/upgrading-mailscanner/</link>
		<comments>http://thern.org/linux-and-freebsd/upgrading-mailscanner/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 08:38:32 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mailscanner]]></category>
		<category><![CDATA[rpm]]></category>
		<category><![CDATA[spamassassin]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=75</guid>
		<description><![CDATA[Easy Upgrading of MailScanner - RPM version (For Redhat/Centos - updated from the MailScanner documentation) 1) Make a backup copy of your current MailScanner (Linux): cp -a /etc/MailScanner /etc/MailScanner.$(date +%Y%m%d) cp -a /usr/lib/MailScanner /usr/lib/MailScanner.$(date +%Y%m%d) cp -a /usr/sbin/MailScanner /usr/sbin/MailScanner.$(date +%Y%m%d) 2) Download the latest version and extract http://mailscanner.info/downloads.html Check the changelog for upgrade notes and [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/upgrading-mailscanner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/dell-1650-server-and-ipmi-support-on-centos-5/</link>
		<comments>http://thern.org/linux-and-freebsd/dell-1650-server-and-ipmi-support-on-centos-5/#comments</comments>
		<pubDate>Thu, 17 Jan 2008 22:25:54 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[general]]></category>
		<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[dell 1650]]></category>
		<category><![CDATA[ipmi]]></category>
		<category><![CDATA[ipmitool]]></category>
		<category><![CDATA[lm_sensors]]></category>
		<category><![CDATA[OpenIPMI]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=64</guid>
		<description><![CDATA[So I bought a Dell 1650 server on ebay for cheap. I loaded it up with three 36gb U160 10,000 RPM SCSI disks in a RAID 5 array, loaded up CentOS 5 and off I went. Once it was at the data centre, I wanted to monitor the system a bit. This meant I wanted [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/dell-1650-server-and-ipmi-support-on-centos-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/linux-and-freebsd/sendmail-premissions-error-stopping-mail-from-sending-on-centos-5-1/</link>
		<comments>http://thern.org/linux-and-freebsd/sendmail-premissions-error-stopping-mail-from-sending-on-centos-5-1/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 22:24:11 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[sendmail]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[permission denied]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=62</guid>
		<description><![CDATA[Really stupid issue with permissions on CentOS 5.1 and real easy fix, since there were improper permissions on the mqueue and clientmqueue directories. The Error message: Tried to send mail via command line using 'mail' command, and it returned this error: can not chdir(/var/spool/clientmqueue/): Permission denied Program mode requires special privileges, e.g., root or TrustedUser. [...]]]></description>
		<wfw:commentRss>http://thern.org/linux-and-freebsd/sendmail-premissions-error-stopping-mail-from-sending-on-centos-5-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>linux &amp; freebsd Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/freebsd/keeping-servers-and-workstations-on-time-using-cron-and-ntpdate/</link>
		<comments>http://thern.org/system-administration/freebsd/keeping-servers-and-workstations-on-time-using-cron-and-ntpdate/#comments</comments>
		<pubDate>Tue, 02 Oct 2007 22:16:17 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[freebsd]]></category>
		<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[cron]]></category>
		<category><![CDATA[ntpdate]]></category>
		<category><![CDATA[time]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=52</guid>
		<description><![CDATA[I'm a fan of having all my computers report the same time, especially when I have to cross reference logs on different servers and require the times to all match up. I've used rdate to update time in the past, but lately have been using ntpdate, which seems to be quite a bit better. One [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/freebsd/keeping-servers-and-workstations-on-time-using-cron-and-ntpdate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
