<?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>SurlyJake &#187; FreeBSD8</title>
	<atom:link href="http://www.surlyjake.com/category/freebsd8/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.surlyjake.com</link>
	<description></description>
	<lastBuildDate>Fri, 30 Dec 2011 15:28:12 +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>ntpq timed out on freeBSD</title>
		<link>http://www.surlyjake.com/2010/09/ntpq-timed-out-on-freebsd/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ntpq-timed-out-on-freebsd</link>
		<comments>http://www.surlyjake.com/2010/09/ntpq-timed-out-on-freebsd/#comments</comments>
		<pubDate>Tue, 07 Sep 2010 18:42:38 +0000</pubDate>
		<dc:creator>jacob</dc:creator>
				<category><![CDATA[FreeBSD8]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[ntp]]></category>
		<category><![CDATA[ntpd]]></category>
		<category><![CDATA[time]]></category>

		<guid isPermaLink="false">http://www.surlyjake.com/?p=662</guid>
		<description><![CDATA[I was running ntpd locally on a server and wanted to check in on ntpd&#8217;s status. ntpq -p was not producing any output even though ntpd was running. # ntpq -p localhost: timed out, nothing received ***Request timed out This is because I had the option &#8220;restrict default ignore&#8221; set in /etc/ntp.conf. ntpq. This makes [...]]]></description>
			<content:encoded><![CDATA[<p>I was running <a href="http://www.surlyjake.com/tag/ntpd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ntpd">ntpd</a> locally on a server and wanted to check in on <a href="http://www.surlyjake.com/tag/ntpd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ntpd">ntpd</a>&#8217;s status. ntpq -p was not producing any output even though <a href="http://www.surlyjake.com/tag/ntpd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ntpd">ntpd</a> was running.</p>
<pre><code># ntpq -p
localhost: timed out, nothing received
***Request timed out</code></pre>
<p>This is because I had the option &#8220;restrict default ignore&#8221; set in /etc/<a href="http://www.surlyjake.com/tag/ntp/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ntp">ntp</a>.conf. ntpq. This makes ntpd ignore EVERYTHING, even queries to the loopback interface. Ntpq queries ntpd over the loopback interface at 127.0.0.1. To allow these local queries, add:</p>
<pre><code> restrict 127.0.0.1</code></pre>
<p>to /etc/ntp.conf, then also add restrict lines for your other upstream ntp servers.</p>
<p>restart ntpd:</p>
<pre><code>/etc/rc.d/ntpd restart</code></pre>
<p>Now ntpq -p will show you status of it&#8217;s peers</p>
<pre><code># ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 dns3.untangle.c .INIT.          16 u    -   64    0    0.000    0.000   0.000
 mirror          .INIT.          16 u    -   64    0    0.000    0.000   0.000
 153.16.4.133    .INIT.          16 u    -   64    0    0.000    0.000   0.000</code></pre>
<div class="none"><div class="g-plusone" data-href="http://www.surlyjake.com/2010/09/ntpq-timed-out-on-freebsd/" size="standard" count="true"></div></div>]]></content:encoded>
			<wfw:commentRss>http://www.surlyjake.com/2010/09/ntpq-timed-out-on-freebsd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updating FreeBSD ports nicely using nice</title>
		<link>http://www.surlyjake.com/2010/06/updating-freebsd-ports-nicely-using-nice/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=updating-freebsd-ports-nicely-using-nice</link>
		<comments>http://www.surlyjake.com/2010/06/updating-freebsd-ports-nicely-using-nice/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 15:34:22 +0000</pubDate>
		<dc:creator>jacob</dc:creator>
				<category><![CDATA[FreeBSD8]]></category>
		<category><![CDATA[Compiling]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[freebsd ports]]></category>
		<category><![CDATA[portupgrade]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.surlyjake.com/?p=595</guid>
		<description><![CDATA[Thanks to: http://scottspare.com/bsdfun/?p=75 for pointing me in the right direction. Compiling port updates can take a while and slow down your server. What you can do is use the &#8216;nice&#8217; utility to force the processes to a lower priority. This will help your server to run almost normally during an update. When you use the [...]]]></description>
			<content:encoded><![CDATA[<p>Thanks to: <a href="http://scottspare.com/bsdfun/?p=75" target="_blank">http://scottspare.com/bsdfun/?p=75</a> for pointing me in the right direction. <a href="http://www.surlyjake.com/tag/compiling/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Compiling">Compiling</a> port updates can take a while and slow down your server. What you can do is use the &#8216;nice&#8217; utility to force the processes to a lower priority. This will help your server to run <em>almost</em> normally during an <a href="http://www.surlyjake.com/tag/update/" class="st_tag internal_tag" rel="tag" title="Posts tagged with update">update</a>.</p>
<p>When you use the &#8216;nice&#8217; command inside of csh or tcsh, you need to mind that you give the full path to the binary so you dont use the built-in &#8216;nice&#8217; command.</p>
<pre><code># /usr/bin/nice -n 10 {your update command}</code></pre>
<p>What i use is:</p>
<pre><code># /usr/bin/nice -n 10 <a href="http://www.surlyjake.com/tag/portupgrade/" class="st_tag internal_tag" rel="tag" title="Posts tagged with portupgrade">portupgrade</a> -aRrP</code></pre>
<p>Man page for &#8216;nice&#8217;: <a href="http://www.freebsd.org/cgi/man.cgi?query=nice&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+8.0-RELEASE&amp;format=html" target="_blank">http://www.freebsd.org/cgi/man.cgi?query=nice&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+8.0-RELEASE&amp;format=html</a></p>
<div class="none"><div class="g-plusone" data-href="http://www.surlyjake.com/2010/06/updating-freebsd-ports-nicely-using-nice/" size="standard" count="true"></div></div>]]></content:encoded>
			<wfw:commentRss>http://www.surlyjake.com/2010/06/updating-freebsd-ports-nicely-using-nice/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Freebsd-update fetch interupted</title>
		<link>http://www.surlyjake.com/2010/06/freebsd-update-fetch-interupted/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=freebsd-update-fetch-interupted</link>
		<comments>http://www.surlyjake.com/2010/06/freebsd-update-fetch-interupted/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 20:38:35 +0000</pubDate>
		<dc:creator>jacob</dc:creator>
				<category><![CDATA[FreeBSD8]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Freebsd-update]]></category>

		<guid isPermaLink="false">http://www.surlyjake.com/?p=590</guid>
		<description><![CDATA[I lost power while freebsd-update fetch was downloading patches up to 8.0-Release-p3. When the server came back online, I ran a freebsd-update fetch again and it still found two files that needed updating. after running freebsd-update install, got this error: # freebsd-update install Installing updates...gunzip: (stdin): unexpected end of file gunzip: (stdin): unexpected end of [...]]]></description>
			<content:encoded><![CDATA[<p>I lost power while <a href="http://www.surlyjake.com/tag/freebsd-update/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Freebsd-update">freebsd-update</a> fetch was downloading patches up to 8.0-Release-p3. When the server came back online, I ran a <a href="http://www.surlyjake.com/tag/freebsd-update/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Freebsd-update">freebsd-update</a> fetch again and it still found two files that needed updating. after running <a href="http://www.surlyjake.com/tag/freebsd-update/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Freebsd-update">freebsd-update</a> install, got this error:</p>
<pre><code># <a href="http://www.surlyjake.com/tag/freebsd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with FreeBSD">freebsd</a>-<a href="http://www.surlyjake.com/tag/update/" class="st_tag internal_tag" rel="tag" title="Posts tagged with update">update</a> install
Installing updates...gunzip: (stdin): unexpected end of file
gunzip: (stdin): unexpected end of file
 done.</code></pre>
<p>I guess a patch archive was corrupted. no problem though, just remove the download:</p>
<pre><code># rm -r /var/db/freebsd-update/files</code></pre>
<p>now you can run</p>
<pre><code># freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 8.0-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 2 files... done.

The following files will be updated as part of updating to 8.0-RELEASE-p3:
/boot/kernel/kernel.symbols
/boot/kernel/nfsclient.ko.symbols
# freebsd-update install
Installing updates... done.
</code></pre>
<p>no problems</p>
<div class="none"><div class="g-plusone" data-href="http://www.surlyjake.com/2010/06/freebsd-update-fetch-interupted/" size="standard" count="true"></div></div>]]></content:encoded>
			<wfw:commentRss>http://www.surlyjake.com/2010/06/freebsd-update-fetch-interupted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ZFS Cant rm: No space left on device</title>
		<link>http://www.surlyjake.com/2010/01/zfs-cant-rm-no-space-left-on-device/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=zfs-cant-rm-no-space-left-on-device</link>
		<comments>http://www.surlyjake.com/2010/01/zfs-cant-rm-no-space-left-on-device/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 22:52:42 +0000</pubDate>
		<dc:creator>jacob</dc:creator>
				<category><![CDATA[FreeBSD8]]></category>
		<category><![CDATA[ZFS]]></category>
		<category><![CDATA[dd]]></category>
		<category><![CDATA[Filesystem]]></category>
		<category><![CDATA[rm command]]></category>

		<guid isPermaLink="false">http://www.surlyjake.com/?p=582</guid>
		<description><![CDATA[If you completely fill up a zfs pool, it wont let you delete files on it. What you CAN do, is pick a scapegoat file to wipe out or remove a snapshot. Then you will be able to use the rm command. what I did: # df -h Filesystem     Size    Used   Avail Capacity  Mounted on [...]]]></description>
			<content:encoded><![CDATA[<p>If you completely fill up a <a href="http://www.surlyjake.com/tag/zfs/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ZFS">zfs</a> pool, it wont let you delete files on it. What you CAN do, is pick a scapegoat file to wipe out or remove a snapshot. Then you will be able to use the <a href="http://www.surlyjake.com/tag/rm-command/" class="st_tag internal_tag" rel="tag" title="Posts tagged with rm command">rm command</a>. what I did:</p>
<pre><code>
# df -h
<a href="http://www.surlyjake.com/tag/filesystem/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Filesystem">Filesystem</a>     Size    Used   Avail Capacity  Mounted on
themirror       39G     39G      0B   100%    /home/jacob/themirror</code>
<code># rm 3gfile
rm: 3gfile: No space left on device</code>
<code># <a href="http://www.surlyjake.com/tag/dd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with dd">dd</a> if=/dev/null of=3gfile
0+0 records in
0+0 records out
0 bytes transferred in 0.000046 secs (0 bytes/sec)</code>
<code># rm 3gfile</code></pre>
<div class="none"><div class="g-plusone" data-href="http://www.surlyjake.com/2010/01/zfs-cant-rm-no-space-left-on-device/" size="standard" count="true"></div></div>]]></content:encoded>
			<wfw:commentRss>http://www.surlyjake.com/2010/01/zfs-cant-rm-no-space-left-on-device/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>FreeBSD error in /boot/loader.conf</title>
		<link>http://www.surlyjake.com/2009/12/freebsd-error-in-bootloader-conf/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=freebsd-error-in-bootloader-conf</link>
		<comments>http://www.surlyjake.com/2009/12/freebsd-error-in-bootloader-conf/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 21:29:41 +0000</pubDate>
		<dc:creator>jacob</dc:creator>
				<category><![CDATA[FreeBSD8]]></category>

		<guid isPermaLink="false">http://www.surlyjake.com/?p=572</guid>
		<description><![CDATA[While experimenting with ZFS in FreeBSD, I made some tweaks to the vk.kmem_size variable in /boot/loader.conf. when setting it like this: #/boot/loader.conf vm.kmem_size="1024" everything worked, but I wanted to see what would happen if i doubled it. Unfortunately, setting vm.kmem_size to 2048 kept the FreeBSD kernel from booting. At startup it would just do this: [...]]]></description>
			<content:encoded><![CDATA[<p>While experimenting with <a href="http://www.surlyjake.com/tag/zfs/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ZFS">ZFS</a> in <a href="http://www.surlyjake.com/tag/freebsd/" class="st_tag internal_tag" rel="tag" title="Posts tagged with FreeBSD">FreeBSD</a>, I made some tweaks to the vk.kmem_size variable in /boot/loader.conf. when setting it like this:</p>
<pre><code>#/boot/loader.conf
vm.kmem_size="1024"</code></pre>
<p>everything worked, but I wanted to see what would happen if i doubled it. Unfortunately, setting vm.kmem_size to 2048 kept the FreeBSD kernel from booting. At startup it would just do this:</p>
<pre><code>panic: kmem_suballoc: bad status return of 3
cpuid = 0</code></pre>
<p>To fix the erroneous variable setting, I had to :</p>
<p>1. Reboot.</p>
<p>2. Wait for the FreeBSD Boot menu. (the screen that lists Default, ACPI disabled, safe, and single user modes)</p>
<p>3. Press 6 to select &#8220;Escape to loader prompt&#8221;</p>
<p>4. At the loader prompt, type &#8220;show&#8221;. This will provide all the default variable settings. press the spacebar to page down. In my case, at the end, the incorrect variable was: vm.kmem_size=&#8221;2048&#8243;.</p>
<p>5. to switch it back and allow the system to boot, type</p>
<pre><code>set (variable)=(correct value)</code></pre>
<p>in my case this was:</p>
<pre><code>set vm.kmem_size=1024M</code></pre>
<p>6. type</p>
<pre><code>boot</code></pre>
<p>When you are finished with all that fun, you should edit the /boot/loader.conf file back so you don&#8217;t have to do this again.<br />
Thanks to &#8220;crsd&#8221; from the FreeBSD IRC channel for the help.</p>
<div class="none"><div class="g-plusone" data-href="http://www.surlyjake.com/2009/12/freebsd-error-in-bootloader-conf/" size="standard" count="true"></div></div>]]></content:encoded>
			<wfw:commentRss>http://www.surlyjake.com/2009/12/freebsd-error-in-bootloader-conf/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

