<?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: Why does htop display an exclamation mark next to uptime?</title>
	<atom:link href="http://blog.beplacid.net/2009/01/14/why-does-htop-display-an-exclamation-mark-next-to-uptime/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.beplacid.net/2009/01/14/why-does-htop-display-an-exclamation-mark-next-to-uptime/</link>
	<description>Musings of technology, sport, life et al</description>
	<lastBuildDate>Tue, 20 Jul 2010 07:53:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SudoSeth &#187; Webserver: 103 Days of Uptime and Counting</title>
		<link>http://blog.beplacid.net/2009/01/14/why-does-htop-display-an-exclamation-mark-next-to-uptime/comment-page-1/#comment-3695</link>
		<dc:creator>SudoSeth &#187; Webserver: 103 Days of Uptime and Counting</dc:creator>
		<pubDate>Thu, 29 Jan 2009 04:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.beplacid.net/?p=62#comment-3695</guid>
		<description>[...] bit of code that does this can be found in the source code of UptimeMeter.c (as I learned from atc): 35 char daysbuf[15]; 36 if (days &gt; 100) { 37 sprintf(daysbuf, “%d days(!), “, days); 38 } [...]</description>
		<content:encoded><![CDATA[<p>[...] bit of code that does this can be found in the source code of UptimeMeter.c (as I learned from atc): 35 char daysbuf[15]; 36 if (days &gt; 100) { 37 sprintf(daysbuf, “%d days(!), “, days); 38 } [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
