<?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 for ~#nixy</title>
	<atom:link href="http://nixy.dk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://nixy.dk</link>
	<description>Nix is sexy</description>
	<lastBuildDate>Fri, 16 Oct 2009 09:11:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on New VPS and the troubles by Garry</title>
		<link>http://nixy.dk/2009/10/16/new-vps-and-the-troubles/comment-page-1/#comment-8199</link>
		<dc:creator>Garry</dc:creator>
		<pubDate>Fri, 16 Oct 2009 09:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/?p=23#comment-8199</guid>
		<description>Glad you like our VPS services, thanks for the kind words!</description>
		<content:encoded><![CDATA[<p>Glad you like our VPS services, thanks for the kind words!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DenyHosts on FreeBSD 6.2 by Scott Spare</title>
		<link>http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/comment-page-1/#comment-5165</link>
		<dc:creator>Scott Spare</dc:creator>
		<pubDate>Sun, 15 Mar 2009 20:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/#comment-5165</guid>
		<description>Great article.  One note that might be of interest: in addition to your suggestions, the denyhosts faq mentions blanking out the BLOCK_SERVICE value when using auxiliary files.
http://denyhosts.sourceforge.net/faq.html#aux

Can anyone comment on why this might be?  

Also, any comments on how to block ALL access from the offending hosts?  This seems doable, but the tutorials and documentation seem to suggest the approach of just blocking ssh.  Maybe this is to prevent a DoS to all your services at once if someone&#039;s injecting code?</description>
		<content:encoded><![CDATA[<p>Great article.  One note that might be of interest: in addition to your suggestions, the denyhosts faq mentions blanking out the BLOCK_SERVICE value when using auxiliary files.<br />
<a href="http://denyhosts.sourceforge.net/faq.html#aux" rel="nofollow">http://denyhosts.sourceforge.net/faq.html#aux</a></p>
<p>Can anyone comment on why this might be?  </p>
<p>Also, any comments on how to block ALL access from the offending hosts?  This seems doable, but the tutorials and documentation seem to suggest the approach of just blocking ssh.  Maybe this is to prevent a DoS to all your services at once if someone&#8217;s injecting code?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by VMWare RTC Meldungen &#187; flocki wills wissen</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-1549</link>
		<dc:creator>VMWare RTC Meldungen &#187; flocki wills wissen</dc:creator>
		<pubDate>Fri, 12 Sep 2008 14:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-1549</guid>
		<description>[...] http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/" rel="nofollow">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by Ben</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-899</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Thu, 03 Jul 2008 13:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-899</guid>
		<description>I&#039;ve been having timing issues with vmplayer on a custom kernel. I have done EVERY possible thing I could think of when building a custom kernel for vmplayer but the time always runs really fast and the reported CPU is much slower than it actually is. I read all of vmware&#039;s documentation and all I found is that the kernel requires the rtc and parallel port support. Using the tsc as the system timer works fine for the guest (with the exception of choppy audio) but performance suffers. I would like to be able to use the hpet. Could you possibly post your entire kernel config? btw, vmware&#039;s documentation for linux is disgusting so I appreciate posts like this.
Thanks,
Ben</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been having timing issues with vmplayer on a custom kernel. I have done EVERY possible thing I could think of when building a custom kernel for vmplayer but the time always runs really fast and the reported CPU is much slower than it actually is. I read all of vmware&#8217;s documentation and all I found is that the kernel requires the rtc and parallel port support. Using the tsc as the system timer works fine for the guest (with the exception of choppy audio) but performance suffers. I would like to be able to use the hpet. Could you possibly post your entire kernel config? btw, vmware&#8217;s documentation for linux is disgusting so I appreciate posts like this.<br />
Thanks,<br />
Ben</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DenyHosts on FreeBSD 6.2 by DenyHosts on FreeBSD 6.2 &#124; FreeBSD - the unknown Giant</title>
		<link>http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/comment-page-1/#comment-875</link>
		<dc:creator>DenyHosts on FreeBSD 6.2 &#124; FreeBSD - the unknown Giant</dc:creator>
		<pubDate>Thu, 26 Jun 2008 21:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/#comment-875</guid>
		<description>[...] Learn how to set it up here         &#171; FreeBSD: the best server OS Google Docs updates &#187; [...]</description>
		<content:encoded><![CDATA[<p>[...] Learn how to set it up here         &laquo; FreeBSD: the best server OS Google Docs updates &raquo; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DenyHosts on FreeBSD 6.2 by Aaron</title>
		<link>http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/comment-page-1/#comment-711</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 28 Apr 2008 20:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/12/denyhosts-on-freebsd-62/#comment-711</guid>
		<description>Great post and thanks!

I wish I could point it at HTTP logs for brute force attacks against my .htaccess
There are an awful lot of people trying to access my phpmyadmin alias.</description>
		<content:encoded><![CDATA[<p>Great post and thanks!</p>
<p>I wish I could point it at HTTP logs for brute force attacks against my .htaccess<br />
There are an awful lot of people trying to access my phpmyadmin alias.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by Rada</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-707</link>
		<dc:creator>Rada</dc:creator>
		<pubDate>Sat, 26 Apr 2008 12:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-707</guid>
		<description>That is very odd. I&#039;ve never - at all - come across this issue with 64-bit architectures.

Did you try poking in your kernel config?</description>
		<content:encoded><![CDATA[<p>That is very odd. I&#8217;ve never &#8211; at all &#8211; come across this issue with 64-bit architectures.</p>
<p>Did you try poking in your kernel config?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by brandon</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-691</link>
		<dc:creator>brandon</dc:creator>
		<pubDate>Thu, 17 Apr 2008 01:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-691</guid>
		<description>revisiting this issue... apparently this isn&#039;t the magic bullet...

/proc$ zcat config.gz &#124;grep CONFIG_RTC
CONFIG_RTC=y
/proc$ zcat config.gz &#124;grep HPET
CONFIG_HPET_EMULATE_RTC=y
/proc$ dmesg &#124; tail -2
rtc: lost some interrupts at 512Hz.
rtc: lost some interrupts at 512Hz.

Hardware is SC1435.
Linux hostname 2.6.22-3-amd64 #1 SMP Mon Nov 12 17:53:18 UTC 2007 x86_64 GNU/Linux

Any other ideas?</description>
		<content:encoded><![CDATA[<p>revisiting this issue&#8230; apparently this isn&#8217;t the magic bullet&#8230;</p>
<p>/proc$ zcat config.gz |grep CONFIG_RTC<br />
CONFIG_RTC=y<br />
/proc$ zcat config.gz |grep HPET<br />
CONFIG_HPET_EMULATE_RTC=y<br />
/proc$ dmesg | tail -2<br />
rtc: lost some interrupts at 512Hz.<br />
rtc: lost some interrupts at 512Hz.</p>
<p>Hardware is SC1435.<br />
Linux hostname 2.6.22-3-amd64 #1 SMP Mon Nov 12 17:53:18 UTC 2007 x86_64 GNU/Linux</p>
<p>Any other ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by Rada</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-582</link>
		<dc:creator>Rada</dc:creator>
		<pubDate>Sun, 09 Mar 2008 13:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-582</guid>
		<description>th3D:
Well, in my situation (With a Dell PowerEdge server), the BIOS didn&#039;t have an option to turn off HPET. Also, why NOT use HPET?</description>
		<content:encoded><![CDATA[<p>th3D:<br />
Well, in my situation (With a Dell PowerEdge server), the BIOS didn&#8217;t have an option to turn off HPET. Also, why NOT use HPET?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickpost: RTC problems in Debian on Dell PowerEdge servers by th3D</title>
		<link>http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/comment-page-1/#comment-580</link>
		<dc:creator>th3D</dc:creator>
		<pubDate>Sun, 09 Mar 2008 04:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://nixy.dk/2007/10/24/quickpost-rtc-problems-in-debian-on-dell-poweredge-servers/#comment-580</guid>
		<description>WHY rebuild kernel when HPET usually can be turned off in BIOS? HPET isnt a requirement but rather a supplement, im sure HPET will be supported in the next major Debian release, until then Debian is still one of the best distros and i hope people dont start recompiling or change distro without taking 30 seconds to look for it in Bios first.</description>
		<content:encoded><![CDATA[<p>WHY rebuild kernel when HPET usually can be turned off in BIOS? HPET isnt a requirement but rather a supplement, im sure HPET will be supported in the next major Debian release, until then Debian is still one of the best distros and i hope people dont start recompiling or change distro without taking 30 seconds to look for it in Bios first.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->