<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Personal Musings for Public Consumption - FreeBSD</title>
    <link>http://sean.chittenden.org/</link>
    <description>Sean's Digital Dumping Ground For Public Information</description>
    <dc:language>en</dc:language>
    <generator>Serendipity  - http://www.s9y.org/</generator>
    <pubDate>Sat, 27 Feb 2010 02:43:27 GMT</pubDate>

    <image>
        <url>http://sean.chittenden.org/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Personal Musings for Public Consumption - FreeBSD - Sean's Digital Dumping Ground For Public Information</title>
        <link>http://sean.chittenden.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Poor man's solution to using APC 3.1.3p1 on FreeBSD...</title>
    <link>http://sean.chittenden.org/archives/2010/02/26/217/Poor-mans-solution-to-using-APC-3.1.3p1-on-FreeBSD....html</link>
            <category>FreeBSD</category>
    
    <comments>http://sean.chittenden.org/archives/2010/02/26/217/Poor-mans-solution-to-using-APC-3.1.3p1-on-FreeBSD....html#comments</comments>
    <wfw:comment>http://sean.chittenden.org/wfwcomment.php?cid=217</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://sean.chittenden.org/rss.php?version=2.0&amp;type=comments&amp;cid=217</wfw:commentRss>
    

    <author>nospam@example.com (Sean Chittenden)</author>
    <content:encoded>
    Rapid fire simple instructions to get APC 3.1.3p1 working on FreeBSD given the port only has 3.0.19. &lt;br /&gt;&lt;a href=&quot;http://sean.chittenden.org/archives/2010/02/26/217/Poor-mans-solution-to-using-APC-3.1.3p1-on-FreeBSD....html#extended&quot;&gt;Continue reading &quot;Poor man&#039;s solution to using APC 3.1.3p1 on FreeBSD...&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 26 Feb 2010 18:43:27 -0800</pubDate>
    <guid isPermaLink="false">http://sean.chittenden.org/archives/2010/02/26/217/guid.html</guid>
    <category>freebsd</category>
<category>php</category>
<category>ports</category>

</item>
<item>
    <title>Linux vs. FreeBSD</title>
    <link>http://sean.chittenden.org/archives/2009/03/24/255/Linux-vs.-FreeBSD.html</link>
            <category>FreeBSD</category>
    
    <comments>http://sean.chittenden.org/archives/2009/03/24/255/Linux-vs.-FreeBSD.html#comments</comments>
    <wfw:comment>http://sean.chittenden.org/wfwcomment.php?cid=255</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://sean.chittenden.org/rss.php?version=2.0&amp;type=comments&amp;cid=255</wfw:commentRss>
    

    <author>nospam@example.com (Sean Chittenden)</author>
    <content:encoded>
    I had a marketing &amp;quot;Ah ha!&amp;quot; moment this morning regarding &amp;linux;&#039;s popularity.  Observe the following: &lt;a href=&quot;http://sean.chittenden.org/exit.php?url_id=32&amp;amp;entry_id=255&quot; title=&quot;http://twitpic.com/2ekek&quot;  onmouseover=&quot;window.status=&#039;http://twitpic.com/2ekek&#039;;return true;&quot; onmouseout=&quot;window.status=&#039;&#039;;return true;&quot;&gt;Linux popularity explained&lt;/a&gt; 
    </content:encoded>

    <pubDate>Tue, 24 Mar 2009 10:00:00 -0700</pubDate>
    <guid isPermaLink="false">http://sean.chittenden.org/archives/2009/03/24/255/guid.html</guid>
    <category>freebsd</category>
<category>linux</category>

</item>
<item>
    <title>gettimeofday(2) == bad; clock_gettime(2) == good.</title>
    <link>http://sean.chittenden.org/archives/2008/06/01/265/gettimeofday2-bad;-clock_gettime2-good..html</link>
            <category>FreeBSD</category>
    
    <comments>http://sean.chittenden.org/archives/2008/06/01/265/gettimeofday2-bad;-clock_gettime2-good..html#comments</comments>
    <wfw:comment>http://sean.chittenden.org/wfwcomment.php?cid=265</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://sean.chittenden.org/rss.php?version=2.0&amp;type=comments&amp;cid=265</wfw:commentRss>
    

    <author>nospam@example.com (Sean Chittenden)</author>
    <content:encoded>
    &lt;p&gt;Finally, a technical post I feel worthy of commenting on.&lt;/p&gt; 
&lt;blockquote&gt;Performance of my application changes from time(3) to gettimeofday(2).  Why? -Joe Open Source Developer&lt;/blockquote&gt; 
&lt;p&gt;Doh!  Really common question and should be an FAQ at this point.... or it is, but an under-published FAQ that only the performance wonks seem to know or run into as an issue.  In short, gettimeofday* == EBAD &amp;amp;&amp;amp; clock_gettime* == EGOOD.  I think the best discussion on this is &lt;a href=&quot;http://sean.chittenden.org/exit.php?url_id=45&amp;amp;entry_id=265&quot; title=&quot;http://people.freebsd.org/~phk/&quot;  onmouseover=&quot;window.status=&#039;http://people.freebsd.org/~phk/&#039;;return true;&quot; onmouseout=&quot;window.status=&#039;&#039;;return true;&quot;&gt;PHK&#039;s&lt;/a&gt; post titled &lt;a href=&quot;http://sean.chittenden.org/exit.php?url_id=39&amp;amp;entry_id=265&quot; title=&quot;http://lists.freebsd.org/mailman/htdig/freebsd-current/2005-October/057280.html&quot;  onmouseover=&quot;window.status=&#039;http://lists.freebsd.org/mailman/htdig/freebsd-current/2005-October/057280.html&#039;;return true;&quot; onmouseout=&quot;window.status=&#039;&#039;;return true;&quot;&gt;Timers and timing, was: &lt;span title=&quot;The king of fail SQL databases&quot; class=&quot;serendipity_glossaryMarkup&quot;&gt;MySQL&lt;/span&gt; Performance 6.0rc1&lt;/a&gt;.  Please read.  Essentially, FreeBSD*&#039;s gettimeofday* syscall is monotonic, highly accurate and precise, and Linux&#039;s is not.  Therefore, Linux&#039;s gettimeofday* syscall is faster and less accurate than FreeBSD*&#039;s.  I happen to agree that gettimeofday* should be monotonic and I take issue with Linux*&#039;s gettimeofday* implementation.  Monotonic time keeping requires CPU synchronization (which gettimeofday* does under FreeBSD* and should be done under all operating systems) and will always be slow as a result.  Most applications that do not require precise time synchronization across threads and CPUs should use clock_gettime* with a &lt;code&gt;clock_id&lt;/code&gt; of &lt;code&gt;CLOCK_REALTIME_FAST&lt;/code&gt;.  Few applications actually need highly precise, highly accurate, monotonic time measurement and instead can skid by with highly precise, accurate, but non-monotomic time keeping.  And now you know.&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://sean.chittenden.org/archives/2008/06/01/265/gettimeofday2-bad;-clock_gettime2-good..html#extended&quot;&gt;Continue reading &quot;gettimeofday(2) == bad; clock_gettime(2) == good.&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 01 Jun 2008 15:46:00 -0700</pubDate>
    <guid isPermaLink="false">http://sean.chittenden.org/archives/2008/06/01/265/guid.html</guid>
    <category>freebsd</category>
<category>linux</category>
<category>programming</category>

</item>

</channel>
</rss>