<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: ASL: Searching</title>
	<atom:link href="http://boredzo.org/blog/archives/2008-01-23/asl-searching/feed" rel="self" type="application/rss+xml" />
	<link>http://boredzo.org/blog/archives/2008-01-23/asl-searching</link>
	<description>The personal weblog of Peter Hosey.</description>
	<lastBuildDate>Tue, 17 Jan 2012 18:19:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Peter Hosey</title>
		<link>http://boredzo.org/blog/archives/2008-01-23/asl-searching/comment-page-1#comment-315992</link>
		<dc:creator>Peter Hosey</dc:creator>
		<pubDate>Thu, 20 May 2010 04:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2008-01-23/asl-searching#comment-315992</guid>
		<description>Cédric Luthi: That&#039;s not the most amusing thing. &lt;a href=&quot;http://opensource.apple.com/source/Libc/Libc-594.1.4/gen/time-fbsd.c&quot; rel=&quot;nofollow&quot;&gt;Look at the implementation of time(3).&lt;/a&gt; ☺</description>
		<content:encoded><![CDATA[<p>Cédric Luthi: That&#8217;s not the most amusing thing. <a href="http://opensource.apple.com/source/Libc/Libc-594.1.4/gen/time-fbsd.c" rel="nofollow">Look at the implementation of time(3).</a> ☺</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cédric Luthi</title>
		<link>http://boredzo.org/blog/archives/2008-01-23/asl-searching/comment-page-1#comment-315891</link>
		<dc:creator>Cédric Luthi</dc:creator>
		<pubDate>Wed, 19 May 2010 17:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2008-01-23/asl-searching#comment-315891</guid>
		<description>As of 10.5.8 and 10.6.3, asl_send uses gettimeofday(2) and falls back to time(3) if gettimeofday fails. I don&#039;t see how gettimeofday could possibly fail.</description>
		<content:encoded><![CDATA[<p>As of 10.5.8 and 10.6.3, asl_send uses gettimeofday(2) and falls back to time(3) if gettimeofday fails. I don&#8217;t see how gettimeofday could possibly fail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Hosey</title>
		<link>http://boredzo.org/blog/archives/2008-01-23/asl-searching/comment-page-1#comment-157763</link>
		<dc:creator>Peter Hosey</dc:creator>
		<pubDate>Thu, 24 Jan 2008 16:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2008-01-23/asl-searching#comment-157763</guid>
		<description>&lt;p&gt;Ahruman: I&#039;ve added a note about that.&lt;/p&gt;

&lt;p&gt;Keep in mind that the actual specification of &lt;code&gt;ASL_KEY_TIME&lt;/code&gt;&#039;s value is not documented anywhere. The only documentation is of its value is the erroneous comment in asl.h. So all I see is a count of seconds since 1970.&lt;/p&gt;

&lt;p&gt;Do you know of a way that I can tell whether it&#039;s giving me leap seconds or not? (Preferably without changing my computer&#039;s clock.)&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Ahruman: I&#8217;ve added a note about that.</p>
<p>Keep in mind that the actual specification of <code>ASL_KEY_TIME</code>&#8216;s value is not documented anywhere. The only documentation is of its value is the erroneous comment in asl.h. So all I see is a count of seconds since 1970.</p>
<p>Do you know of a way that I can tell whether it&#8217;s giving me leap seconds or not? (Preferably without changing my computer&#8217;s clock.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahruman</title>
		<link>http://boredzo.org/blog/archives/2008-01-23/asl-searching/comment-page-1#comment-157710</link>
		<dc:creator>Ahruman</dc:creator>
		<pubDate>Thu, 24 Jan 2008 11:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2008-01-23/asl-searching#comment-157710</guid>
		<description>Massive super-nitpick: Unix time is not the number of seconds since the epoch. It’s the number of nominal (clock) seconds since the epoch. This difference (currently about 25 seconds) matters, because Unix time does not increase monotonously – it skips negative seconds and repeats positive leap seconds. If you’re expecting, say, log messages to always be in-order based on Unix time, you’re setting yourself up for a potential failure in the middle of the night once every few years.</description>
		<content:encoded><![CDATA[<p>Massive super-nitpick: Unix time is not the number of seconds since the epoch. It’s the number of nominal (clock) seconds since the epoch. This difference (currently about 25 seconds) matters, because Unix time does not increase monotonously – it skips negative seconds and repeats positive leap seconds. If you’re expecting, say, log messages to always be in-order based on Unix time, you’re setting yourself up for a potential failure in the middle of the night once every few years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.132 seconds -->

