<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Blog update</title>
	<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/</link>
	<description>I am an astronomer, writer, and skeptic. I likes reality the way it is, and I aims to keep it that way. My real name is Phil Plait, and I run the Bad Astronomy blog.</description>
	<pubDate>Sun, 05 Jul 2009 20:56:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Greg in Austin</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76381</link>
		<dc:creator>Greg in Austin</dc:creator>
		<pubDate>Fri, 14 Mar 2008 20:04:27 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76381</guid>
		<description>BA, I still experience issues where your site is slow to load, or completely unresponsive. Just now, when I tried to get to this post, I received this error:

"Couldn't write to: /var/www/vhosts/badastronomy.com/httpdocs/bablog/wp-content/cache/wp-cache-c4523ff689e59b577ba1f8009a01bf52.html"

It happens with both Firefox and Internet Exploder. Of course, during the day I'm behind a corporate firewall, which could be an issue. However, I also read your blog at home, and it too sometimes hangs.

If I can see any more error messages, I'll let you know.

8)</description>
		<content:encoded><![CDATA[<p>BA, I still experience issues where your site is slow to load, or completely unresponsive. Just now, when I tried to get to this post, I received this error:</p>
<p>&#8220;Couldn&#8217;t write to: /var/www/vhosts/badastronomy.com/httpdocs/bablog/wp-content/cache/wp-cache-c4523ff689e59b577ba1f8009a01bf52.html&#8221;</p>
<p>It happens with both Firefox and Internet Exploder. Of course, during the day I&#8217;m behind a corporate firewall, which could be an issue. However, I also read your blog at home, and it too sometimes hangs.</p>
<p>If I can see any more error messages, I&#8217;ll let you know.<br />
 <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: natefoo</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76380</link>
		<dc:creator>natefoo</dc:creator>
		<pubDate>Fri, 14 Mar 2008 03:11:28 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76380</guid>
		<description>"IIRC you don’t need to reboot, but can clear out the current mappings by some abstruse command. As I remember it I had to do that on some machines on local nets when rebooting didn’t help. (Windooze machines and their little Registry, of course!)"

lookupd -flushcache

"It’s BSD Unix based with a kernal called, appropriately enough for this blog, Darwin."

Kernel is mach, BSD "distro" is Darwin, but who's keeping track. ;)</description>
		<content:encoded><![CDATA[<p>&#8220;IIRC you don’t need to reboot, but can clear out the current mappings by some abstruse command. As I remember it I had to do that on some machines on local nets when rebooting didn’t help. (Windooze machines and their little Registry, of course!)&#8221;</p>
<p>lookupd -flushcache</p>
<p>&#8220;It’s BSD Unix based with a kernal called, appropriately enough for this blog, Darwin.&#8221;</p>
<p>Kernel is mach, BSD &#8220;distro&#8221; is Darwin, but who&#8217;s keeping track. <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonStrickland</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76379</link>
		<dc:creator>JonStrickland</dc:creator>
		<pubDate>Thu, 13 Mar 2008 15:27:29 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76379</guid>
		<description>I'm glad your new digs are beefy, because I cited and linked back to the blog as part of an article I wrote called "Top 10 Space Conspiracy Theories" (not yet published).  Hopefully it'll drive more readers to your blog, which I find to be an invaluable resource both for information and entertainment.  Keep up the great work!</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad your new digs are beefy, because I cited and linked back to the blog as part of an article I wrote called &#8220;Top 10 Space Conspiracy Theories&#8221; (not yet published).  Hopefully it&#8217;ll drive more readers to your blog, which I find to be an invaluable resource both for information and entertainment.  Keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fraser Cain</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76378</link>
		<dc:creator>Fraser Cain</dc:creator>
		<pubDate>Thu, 13 Mar 2008 02:42:38 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76378</guid>
		<description>We're now running on a Xeon 5100 server with 4GB of RAM. Of course it's Linux. :-) I'm not sure how much faster it is, but it's certainly taking on triple the load without a problem.

Phil and I wanted to see how well it would withstand a Digg, and we got it last night. Of course, we didn't expect his biggest Digg ever with the Mythbusters post. It was like hoping for a breeze to test your kite and getting a hurricane.

The server went through the load perfectly. No slowdown at any time, even though there were many, many simultaneous users.

It's funny how technical you have to be to just run a successful blog. There's no way we could afford to run our sites these days if we weren't able to manage them ourselves.</description>
		<content:encoded><![CDATA[<p>We&#8217;re now running on a Xeon 5100 server with 4GB of RAM. Of course it&#8217;s Linux. <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> I&#8217;m not sure how much faster it is, but it&#8217;s certainly taking on triple the load without a problem.</p>
<p>Phil and I wanted to see how well it would withstand a Digg, and we got it last night. Of course, we didn&#8217;t expect his biggest Digg ever with the Mythbusters post. It was like hoping for a breeze to test your kite and getting a hurricane.</p>
<p>The server went through the load perfectly. No slowdown at any time, even though there were many, many simultaneous users.</p>
<p>It&#8217;s funny how technical you have to be to just run a successful blog. There&#8217;s no way we could afford to run our sites these days if we weren&#8217;t able to manage them ourselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George E. Martin</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76377</link>
		<dc:creator>George E. Martin</dc:creator>
		<pubDate>Thu, 13 Mar 2008 01:26:15 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76377</guid>
		<description>Phil said:

"However (Warning: tech geekery ahoy!) to move a site to a different location you have to let all the computers on the planet know it. We updated the Domain Name Servers, but that takes a few hours sometimes to propagate throughout the web."

A little more "tech geekery". The maximum time a change in a DNS record should take to propagate through the Internet is the TTL (Time To Live) value of the old DNS record. Name servers typically cache DNS records for the TTL period before looking up the record again.

Because of this, when it is known in advance that a DNS record will be changed, the owner of the DNS record will lower the normal TTL of the record sometime in advance before making the change. Thus when the change is made, it propagates known more quickly. Of course this lowering is not always possible.

Playing games:

[xxxxxx:~] xxxxxx% dig www.badastronomy.com

; &#60;&#62; DiG 9.4.1-P1 &#60;&#62; www.badastronomy.com
;; global options:  printcmd
;; Got answer:
;; -&#62;&#62;HEADER&#60;&#60;- opcode: QUERY, status: NOERROR, id: 918
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;www.badastronomy.com.		IN	A

;; ANSWER SECTION:
www.badastronomy.com.	68037	IN	A	67.228.209.248

The value 68037 is the current timeout value, in seconds, in the cache of the local name server, decrementing from the time it last looked up www.badastronomy.com. A short time later:

;; ANSWER SECTION:
www.badastronomy.com.	67950	IN	A	67.228.209.248

Given the value above, I would guess the TTL for www.badastronomy.com 'is 86400 seconds, or one day.

  George</description>
		<content:encoded><![CDATA[<p>Phil said:</p>
<p>&#8220;However (Warning: tech geekery ahoy!) to move a site to a different location you have to let all the computers on the planet know it. We updated the Domain Name Servers, but that takes a few hours sometimes to propagate throughout the web.&#8221;</p>
<p>A little more &#8220;tech geekery&#8221;. The maximum time a change in a DNS record should take to propagate through the Internet is the TTL (Time To Live) value of the old DNS record. Name servers typically cache DNS records for the TTL period before looking up the record again.</p>
<p>Because of this, when it is known in advance that a DNS record will be changed, the owner of the DNS record will lower the normal TTL of the record sometime in advance before making the change. Thus when the change is made, it propagates known more quickly. Of course this lowering is not always possible.</p>
<p>Playing games:</p>
<p>[xxxxxx:~] xxxxxx% dig <a href="http://www.badastronomy.com" rel="nofollow">www.badastronomy.com</a></p>
<p>; &lt;&gt; DiG 9.4.1-P1 &lt;&gt; <a href="http://www.badastronomy.com" rel="nofollow">www.badastronomy.com</a><br />
;; global options:  printcmd<br />
;; Got answer:<br />
;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 918<br />
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2</p>
<p>;; QUESTION SECTION:<br />
;www.badastronomy.com.		IN	A</p>
<p>;; ANSWER SECTION:<br />
<a href="http://www.badastronomy.com." rel="nofollow">www.badastronomy.com.</a>	68037	IN	A	67.228.209.248</p>
<p>The value 68037 is the current timeout value, in seconds, in the cache of the local name server, decrementing from the time it last looked up <a href="http://www.badastronomy.com." rel="nofollow">www.badastronomy.com.</a> A short time later:</p>
<p>;; ANSWER SECTION:<br />
<a href="http://www.badastronomy.com." rel="nofollow">www.badastronomy.com.</a>	67950	IN	A	67.228.209.248</p>
<p>Given the value above, I would guess the TTL for <a href="http://www.badastronomy.com" rel="nofollow">www.badastronomy.com</a> &#8216;is 86400 seconds, or one day.</p>
<p>  George</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MandyDax</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76374</link>
		<dc:creator>MandyDax</dc:creator>
		<pubDate>Wed, 12 Mar 2008 23:40:36 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76374</guid>
		<description>Yay, BEEFY server!</description>
		<content:encoded><![CDATA[<p>Yay, BEEFY server!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quiet_Desperation</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76376</link>
		<dc:creator>Quiet_Desperation</dc:creator>
		<pubDate>Wed, 12 Mar 2008 23:37:20 +0000</pubDate>
		<guid>http://blogs.discovermagazine.com/badastronomy/2008/03/12/blog-update/#comment-76376</guid>
		<description>&lt;i&gt;Um, isn’t ol’ Mac unix based now? Roughly Linux ...&lt;/i&gt;

It's BSD Unix based with a kernal called, appropriately enough for this blog, Darwin.

The mascot is Hexley, a platypus. ;-)

&lt;i&gt;with a pretty hood and no easy way to tinker with the engine? &lt;/i&gt;

Apple releases the kernal under the Apple Public Source License which has the approval of the Free Software Foundation as a free software license.

Releases available here:
http://www.opensource.apple.com/darwinsource/

The "pretty hood" is Aqua and *that* part is proprietray, but you can run X11 with Darwin.</description>
		<content:encoded><![CDATA[<p><i>Um, isn’t ol’ Mac unix based now? Roughly Linux &#8230;</i></p>
<p>It&#8217;s BSD Unix based with a kernal called, appropriately enough for this blog, Darwin.</p>
<p>The mascot is Hexley, a platypus. <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
<i>with a pretty hood and no easy way to tinker with the engine? </i></p>
<p>Apple releases the kernal under the Apple Public Source License which has the approval of the Free Software Foundation as a free software license.</p>
<p>Releases available here:<br />
<a href="http://www.opensource.apple.com/darwinsource/" rel="nofollow">http://www.opensource.apple.com/darwinsource/</a></p>
<p>The &#8220;pretty hood&#8221; is Aqua and *that* part is proprietray, but you can run X11 with Darwin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
