<?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>Solutions Log &#187; Linux</title>
	<atom:link href="http://solutions.unixsherpa.com/category/os/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutions.unixsherpa.com</link>
	<description>by Dan Reiland</description>
	<lastBuildDate>Fri, 16 Apr 2010 20:28:57 +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>xinetd per_source limit issues</title>
		<link>http://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/</link>
		<comments>http://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 09:32:34 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[xinetd]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=241</guid>
		<description><![CDATA[Issue: Users note availability issues when accessing services backed by xinetd (subversion, rsync, etc.) Identification: Syslog on the affected server will present multiple lines containing daemon per_source_limit for 0.0.0.0. Cause: You have exceeded per_source_limit defaults imposed by your xinetd configuration. Many distributions include per_source limits that may not be suitable for your use case. Evaluate [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
Users note availability issues when accessing services backed by xinetd (subversion, rsync, etc.)</p>
<p><strong>Identification:</strong><br />
Syslog on the affected server will present multiple lines containing <code class="codecolorer text twitlight"><span class="text">daemon per_source_limit for 0.0.0.0</span></code>.</p>
<p><strong>Cause:</strong><br />
You have exceeded per_source_limit defaults imposed by your xinetd configuration. Many distributions include per_source limits that may not be suitable for your use case. Evaluate your needs carefully.</p>
<p><strong>Resolution:</strong><br />
Modify the default setting for per_source in <code class="codecolorer text twitlight"><span class="text">/etc/xinetd.conf</span></code> or modify the service specific configuration (recommended) under <code class="codecolorer text twitlight"><span class="text">/etc/xinet.d</span></code>. per_source limits may be set as follows:</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">per_source = 10</div></div>
<p>per_source may be set to an integer or UNLIMITED (the number represents the number of connections allowed per host). A sensible fixed value is <strong>always</strong> better than UNLIMITED.</p>
<p><em>Reference:</em> xinetd.conf(5)</p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Replace Pipes with Tabs in a Delimited File</title>
		<link>http://solutions.unixsherpa.com/2009/12/04/replace-pipes-with-tabs-in-a-delimited-file/</link>
		<comments>http://solutions.unixsherpa.com/2009/12/04/replace-pipes-with-tabs-in-a-delimited-file/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 20:44:37 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[Regular Expression]]></category>
		<category><![CDATA[Shell]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=224</guid>
		<description><![CDATA[Issue: It is often necessary to replace delimiters in a file with a form the receiving party expects. sed is my favorite method of meeting the need. Solution: Replace double pipes with tabs sed 's/&#124;&#124;/ &#160; &#160; &#160; &#160; &#160; /g' file.in &#62; file.out Note: If you find the tab key simply does not work, [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
It is often necessary to replace delimiters in a file with a form the receiving party expects. sed is my favorite method of meeting the need.</p>
<p><strong>Solution:</strong><br />
Replace double pipes with tabs</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #c20cb9; font-weight: bold;">sed</span> <span style="color: #ff0000;">'s/||/ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; /g'</span> file.in <span style="color: #000000; font-weight: bold;">&gt;</span> file.out</div></div>
<p><em>Note: If you find the tab key simply does not work, try CTRL+V+I from your terminal.</em><br />
<em>Reference: <a href="http://forums.devshed.com/unix-help-35/replacing-tabs-with-spaces-372623.html">http://forums.devshed.com/unix-help-35/replacing-tabs-with-spaces-372623.html</a></em></p>
<p><strong>Caveats:</strong><br />
Special consideration (and a regex) will be required for data where delimiters are present in the data itself. Consider your use case and apply appropriately.</p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/12/04/replace-pipes-with-tabs-in-a-delimited-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a pidof command to find PID numbers easily</title>
		<link>http://solutions.unixsherpa.com/2009/10/07/create-a-pidof-command-to-find-pid-numbers-easily/</link>
		<comments>http://solutions.unixsherpa.com/2009/10/07/create-a-pidof-command-to-find-pid-numbers-easily/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 20:30:44 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Shell]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[init]]></category>
		<category><![CDATA[pid]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=205</guid>
		<description><![CDATA[Most UNIX environments include the pidof command which is put to use whenever one needs to quickly determine, by name, the pid of a running program. Apple's Mac OS X lacks the pidof command, however, one may approximate its function with the following shell script: #!/bin/sh ps axc&#124;awk &#34;{if (\$5==\&#34;$1\&#34;) print \$1}&#34;; Save the script [...]]]></description>
			<content:encoded><![CDATA[<p><em>Most</em> UNIX environments include the pidof command which is put to use whenever one needs to quickly determine, by name, the pid of a running program. Apple's Mac OS X lacks the pidof command, however, one may approximate its function with the following shell script:</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #666666; font-style: italic;">#!/bin/sh</span><br />
<span style="color: #c20cb9; font-weight: bold;">ps</span> axc<span style="color: #000000; font-weight: bold;">|</span><span style="color: #c20cb9; font-weight: bold;">awk</span> <span style="color: #ff0000;">&quot;{if (<span style="color: #000099; font-weight: bold;">\$</span>5==<span style="color: #000099; font-weight: bold;">\&quot;</span>$1<span style="color: #000099; font-weight: bold;">\&quot;</span>) print <span style="color: #000099; font-weight: bold;">\$</span>1}&quot;</span>;</div></div>
<p>Save the script as /bin/pidof and be sure to set its executable bit:</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #c20cb9; font-weight: bold;">chmod</span> a+x <span style="color: #000000; font-weight: bold;">/</span>bin<span style="color: #000000; font-weight: bold;">/</span><span style="color: #c20cb9; font-weight: bold;">pidof</span></div></div>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/10/07/create-a-pidof-command-to-find-pid-numbers-easily/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Strip empty (null) lines from a file</title>
		<link>http://solutions.unixsherpa.com/2009/10/06/strip-empty-null-lines-from-a-file/</link>
		<comments>http://solutions.unixsherpa.com/2009/10/06/strip-empty-null-lines-from-a-file/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 18:12:06 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Shell]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[sed]]></category>
		<category><![CDATA[text processing]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=203</guid>
		<description><![CDATA[sed meets the need; the recipe follows: sed '/^$/d' filename]]></description>
			<content:encoded><![CDATA[<p>sed meets the need; the recipe follows:</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #c20cb9; font-weight: bold;">sed</span> <span style="color: #ff0000;">'/^$/d'</span> filename</div></div>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/10/06/strip-empty-null-lines-from-a-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable disk checking during boot on Linux systems</title>
		<link>http://solutions.unixsherpa.com/2009/08/27/disable-disk-checking-during-boot-on-linux-systems/</link>
		<comments>http://solutions.unixsherpa.com/2009/08/27/disable-disk-checking-during-boot-on-linux-systems/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 19:39:46 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[ext2]]></category>
		<category><![CDATA[ext3]]></category>
		<category><![CDATA[ext4]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[fsck]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=190</guid>
		<description><![CDATA[Issue: Linux (appropriately) checks filesystems after a number of boot cycles. Cause: This is by design. By default, ext[2,3,4] filesystems are automatically checked every 34 mounts or 180 days (whichever comes first). Resolution: In some cases (ephemeral machine instances in a cloud) this behavior is undesirable. It may be tuned with the following: To disable [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
Linux (appropriately) checks filesystems after a number of boot cycles.</p>
<p><strong>Cause:</strong><br />
This is by design. By default, ext[2,3,4] filesystems are automatically checked every 34 mounts or 180 days (whichever comes first).</p>
<p><strong>Resolution:</strong><br />
In some cases (ephemeral machine instances in a cloud) this behavior is undesirable. It may be tuned with the following:</p>
<p>To disable it use the following at the terminal:</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">tune2fs <span style="color: #660033;">-c</span> <span style="color: #000000;">0</span> <span style="color: #660033;">-i</span> <span style="color: #000000;">0</span> <span style="color: #000000; font-weight: bold;">/</span>dev<span style="color: #000000; font-weight: bold;">/</span>hdXY</div></div>
<p>Set it to check after 30 system boots</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">tune2fs <span style="color: #660033;">-c</span> <span style="color: #000000;">30</span> <span style="color: #660033;">-i</span> <span style="color: #000000;">0</span> <span style="color: #000000; font-weight: bold;">/</span>dev<span style="color: #000000; font-weight: bold;">/</span>hdXY</div></div>
<p>Also ensure that your /etc/fstab file reflects a similar setting. The sixth column should contain a 0 (never check) rather than a 1 (check at boot).</p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/08/27/disable-disk-checking-during-boot-on-linux-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>C compiler cannot create executables received after emerge world</title>
		<link>http://solutions.unixsherpa.com/2009/08/19/c-compiler-cannot-create-executables-received-after-emerge-world/</link>
		<comments>http://solutions.unixsherpa.com/2009/08/19/c-compiler-cannot-create-executables-received-after-emerge-world/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 14:56:51 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=169</guid>
		<description><![CDATA[Issue: When attempting to emerge a new package after a recent emerge -DunNv world the new package emerge fails with: . . . checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for builtin ELF support... yes checking for ELF core file support... yes checking for file formats [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
When attempting to emerge a new package after a recent <code class="codecolorer bash twitlight"><span class="bash">emerge <span style="color: #660033;">-DunNv</span> world</span></code> the new package emerge fails with:</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">. . .<br />
checking whether make sets $(MAKE)... yes<br />
checking whether to enable maintainer-specific portions of Makefiles... no<br />
checking for builtin ELF support... yes<br />
checking for ELF core file support... yes<br />
checking for file formats in man section 5... no<br />
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc<br />
checking for C compiler default output file name... <br />
configure: error: C compiler cannot create executables<br />
See `config.log' for more details.<br />
. . .</div></div>
<p><strong>Cause:</strong><br />
The issue is related to gcc being upgraded as part of a previously executed emerge world. The <em>/etc/ld.so.conf</em> and <em>/etc/env.d/05gcc-i686-pc-linux-gnu</em> files no longer point to valid gcc library and binary paths.</p>
<p><strong>Resolution:</strong><br />
Gentoo provides the <em>gcc-config</em> command to set the active gcc compiler profile.</p>
<p><em>Sample gcc-config run to list the available gcc profiles and set the active profile to option 1:</em></p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">root # gcc-config -l<br />
&nbsp;[1] i686-pc-linux-gnu-4.3.2 *<br />
root # gcc-config 1<br />
&nbsp;* Switching native-compiler to i686-pc-linux-gnu-4.3.2 ... &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [ ok ]</div></div>
<p>Reference: <a href="http://forums.gentoo.org/viewtopic.php?t=27486&#038;highlight=gcc">http://forums.gentoo.org/viewtopic.php?t=27486&#038;highlight=gcc</a></p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/08/19/c-compiler-cannot-create-executables-received-after-emerge-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a Large File For Testing</title>
		<link>http://solutions.unixsherpa.com/2009/08/13/create-a-large-file-for-testing/</link>
		<comments>http://solutions.unixsherpa.com/2009/08/13/create-a-large-file-for-testing/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 15:23:33 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=162</guid>
		<description><![CDATA[Issue: Often you need a set of variable sized files for testing a particular scenario. Generating test data is a painless endeavor. Resolution: The Unix dd command is perfectly suited to dispatch this need. dd if=/dev/zero of=~/testfile.txt bs=1m count=5 The above command will create a 5 megabyte file full of zeroes. Lovely. You may adjust [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
Often you need a set of variable sized files for testing a particular scenario. Generating test data is a painless endeavor.</p>
<p><strong>Resolution:</strong><br />
The Unix dd command is perfectly suited to dispatch this need.</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #c20cb9; font-weight: bold;">dd</span> <span style="color: #007800;">if</span>=<span style="color: #000000; font-weight: bold;">/</span>dev<span style="color: #000000; font-weight: bold;">/</span>zero <span style="color: #007800;">of</span>=~<span style="color: #000000; font-weight: bold;">/</span>testfile.txt <span style="color: #007800;">bs</span>=1m <span style="color: #007800;">count</span>=<span style="color: #000000;">5</span></div></div>
<p>The above command will create a 5 megabyte file full of zeroes. Lovely. You may adjust the count (or blocksize) to achieve the results you desire. This data also achieves stellar compression ratios based on its content.</p>
<p>One could also create a test file full of pseudo random data by pointing <em>if</em> to /dev/urandom.</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #c20cb9; font-weight: bold;">dd</span> <span style="color: #007800;">if</span>=<span style="color: #000000; font-weight: bold;">/</span>dev<span style="color: #000000; font-weight: bold;">/</span>urandom <span style="color: #007800;">of</span>=~<span style="color: #000000; font-weight: bold;">/</span>testfile.txt <span style="color: #007800;">bs</span>=1m <span style="color: #007800;">count</span>=<span style="color: #000000;">5</span></div></div>
<p><a href="http://en.wikipedia.org/wiki//dev/random">Explanation of /dev/urandom</a></p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/08/13/create-a-large-file-for-testing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Remote Mirroring Using nc and dd</title>
		<link>http://solutions.unixsherpa.com/2009/08/10/remote-mirroring-using-nc-and-dd/</link>
		<comments>http://solutions.unixsherpa.com/2009/08/10/remote-mirroring-using-nc-and-dd/#comments</comments>
		<pubDate>Mon, 10 Aug 2009 16:58:06 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[netcat]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=160</guid>
		<description><![CDATA[You can use the dd and nc commands for exact disk mirroring from one server to another. The following commands send data from Server1 to Server2: 12Server2# nc -l 12345 &#124; dd of=/dev/sdb Server1# dd if=/dev/sda &#124; nc server2 12345 Make sure that you issue Server2's command first so that it's listening on port 12345 [...]]]></description>
			<content:encoded><![CDATA[<p>You can use the dd and nc commands for exact disk mirroring from one server to another. The following commands send data from Server1 to Server2:</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br />2<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">Server2# nc -l 12345 | dd of=/dev/sdb<br />
Server1# dd if=/dev/sda | nc server2 12345</div></td></tr></tbody></table></div>
<p>Make sure that you issue Server2's command first so that it's listening on port 12345 when Server1 starts sending its data.</p>
<p>Unless you're sure that the disk is not being modified, it's better to boot Server1 from a RescueCD or LiveCD to do the copy. </p>
<p>Reference: <a href="http://www.linuxjournal.com/content/tech-tip-remote-mirroring-using-nc-and-dd">http://www.linuxjournal.com/content/tech-tip-remote-mirroring-using-nc-and-dd</a></p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/08/10/remote-mirroring-using-nc-and-dd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerDNS continually dies after creating a slave zone</title>
		<link>http://solutions.unixsherpa.com/2009/07/29/powerdns-continually-dies-after-creating-a-slave-zone/</link>
		<comments>http://solutions.unixsherpa.com/2009/07/29/powerdns-continually-dies-after-creating-a-slave-zone/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 17:19:20 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[powerdns]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=156</guid>
		<description><![CDATA[Issue: When PowerDNS is configured for a sqlite or sqlite3 backend and a slave zone is added, the PowerDNS daemon continually dies and respawns. This loop persists until the daemon is forcibly terminated. My logs showed the following: Jul 29 12:12:38 localhost pdns[14465]: PowerDNS 2.9.22 (C) 2001-2009 PowerDNS.COM BV (Jul 29 2009, 04:47:43, gcc 4.3.3) [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
When PowerDNS is configured for a sqlite or sqlite3 backend and a slave zone is added, the PowerDNS daemon continually dies and respawns. This loop persists until the daemon is forcibly terminated.</p>
<p>My logs showed the following:</p>
<pre>
Jul 29 12:12:38 localhost pdns[14465]: PowerDNS 2.9.22 (C) 2001-2009 PowerDNS.COM BV (Jul 29 2009, 04:47:43, gcc 4.3.3) starting up
Jul 29 12:12:38 localhost pdns[14465]: PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
Jul 29 12:12:38 localhost pdns[14465]: DNS Proxy launched, local port 22293, remote 192.168.8.1:53
Jul 29 12:12:38 localhost pdns[14465]: Launched webserver on 0.0.0.0:8081
Jul 29 12:12:38 localhost pdns[14465]: Master/slave communicator launching
Jul 29 12:12:38 localhost pdns[14465]: Creating backend connection for TCP
Jul 29 12:12:38 localhost pdns[14465]: gsqlite3: connection to '/var/lib/powerdns/pdns.db' succesful
Jul 29 12:12:38 localhost pdns[14465]: gsqlite3: connection to '/var/lib/powerdns/pdns.db' succesful
Jul 29 12:12:38 localhost pdns[14465]: About to create 3 backend threads for UDP
Jul 29 12:12:38 localhost pdns[14465]: gsqlite3: connection to '/var/lib/powerdns/pdns.db' succesful
Jul 29 12:12:38 localhost pdns[14465]: 1 slave domain needs checking
Jul 29 12:12:38 localhost pdns[14465]: Domain domain.local is stale, master serial 349, our serial 0
Jul 29 12:12:38 localhost pdns[14465]: Initiating transfer of 'domain.local' from remote '192.168.8.40'
Jul 29 12:12:38 localhost pdns[14465]: gsqlite3: connection to '/var/lib/powerdns/pdns.db' succesful
Jul 29 12:12:38 localhost pdns[14465]: AXFR started for 'domain.local', transaction started
Jul 29 12:12:38 localhost pdns[14465]: Communicator thread died because of error: Database failed to start transaction: Error while retrieving SQLite query results
</pre>
<p><strong>Cause:</strong><br />
The PowerDNS sqlite and sqlite3 backends do not support slave zones as of v.2.9.22</p>
<p><strong>Resolution:</strong><br />
Configure PowerDNS to use a different database backend: MySQL, PostgreSQL, Oracle, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/07/29/powerdns-continually-dies-after-creating-a-slave-zone/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>rsync failed to set times on [filename]</title>
		<link>http://solutions.unixsherpa.com/2009/07/09/rsync-failed-to-set-times-on-filename/</link>
		<comments>http://solutions.unixsherpa.com/2009/07/09/rsync-failed-to-set-times-on-filename/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 02:34:52 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Apple OSX]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Shell]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[rsync]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=71</guid>
		<description><![CDATA[This error occurs because the version of rsync on the system cannot preserve modified times for directories. Run rsync with the following arguments to suppress this warning: rsync -avrPO ./source/* ./destination Explanation of switches: 12345a -&#62; Archive mode (do not preserve hard links, ACLs, or extended attributes) v -&#62; Verbose (I like to know what [...]]]></description>
			<content:encoded><![CDATA[<p>This error occurs because the version of rsync on the system cannot preserve modified times for directories. </p>
<p>Run rsync with the following arguments to suppress this warning:</p>
<pre>
 rsync -avrPO ./source/* ./destination
</pre>
<p>Explanation of switches:</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br />2<br />3<br />4<br />5<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">a -&gt; Archive mode (do not preserve hard links, ACLs, or extended attributes)<br />
v -&gt; Verbose (I like to know what is happening)<br />
r -&gt; Copy directories recursively<br />
P -&gt; Equivalent to --partial --progress (for long transfers that may be interrupted)<br />
O -&gt; Omit directories from times</div></td></tr></tbody></table></div>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/07/09/rsync-failed-to-set-times-on-filename/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
